View CY7C63813-PXC_1174925.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

CY7C63310 CY7C638xx
enCoReTM II Low-Speed USB Peripheral Controller
1.0 Features
-- 4 I/O pins with 3.3V logic levels -- Each 3.3V pin supports high-impedance input, internal pull up, open drain output or traditional CMOS output * SPI serial communication -- Master or slave operation -- Configurable up to 4 Mbit/second transfers in the master mode -- Supports half duplex single data line mode for optical sensors * 2-channel 8-bit or 1-channel 16-bit capture timer registers. Capture timer registers store both rising and falling edge times -- Two registers each for two input pins -- Separate registers for rising and falling edge capture -- Simplifies interface to RF inputs for wireless applications * Internal low-power wake-up timer during suspend mode -- Periodic wake-up with no external components * 12-bit Programmable Interval Timer with interrupts * Advanced development tools based on Cypress MicroSystems PSoCTM tools * Watchdog timer (WDT) * Low-voltage detection with user-configurable threshold voltages * Operating voltage from 4.0V to 5.5VDC * Operating temperature from 0-70C * Available in 16/18-pin PDIP, 16/18/24-pin SOIC, 24-pin QSOP and 32-lead QFN packages * Industry standard programmer support * enCoReTM II USB--"enhanced Component Reduction" -- Crystalless oscillator with support for an external clock. The internal oscillator eliminates the need for an external crystal or resonator -- Two internal 3.3V regulators and internal USB pull-up resistor -- Configurable IO for real-world interface without external components * USB Specification Compliance -- Conforms to USB Specification, Version 2.0 -- Conforms to USB HID Specification, Version 1.1 -- Supports one Low-Speed USB device address -- Supports one control endpoint and two data endpoints -- Integrated USB transceiver with dedicated 3.3V regulator for USB signalling and D- pull up. * Enhanced 8-bit microcontroller -- Harvard architecture -- M8C CPU speed can be up to 24 MHz or sourced by an external clock signal * Internal memory -- Up to 256 bytes of RAM -- Up to eight Kbytes of Flash including EEROM emulation * Interface can autoconfigure to operate as PS/2 or USB -- No external components for switching between PS/2 and USB modes -- No GPIO pins needed to manage dual-mode capability * Low power consumption -- Typically 10 mA at 6 MHz -- 10 A sleep * In-system re-programmability -- Allows easy firmware update * General purpose I/O ports -- Up to 20 General Purpose I/O (GPIO) pins -- High current drive on GPIO pins. Configurable 8- or 50mA/pin current sink on designated pins -- Each GPIO port supports high-impedance inputs, configurable pull up, open drain output, CMOS/TTL inputs, and CMOS output -- Maskable interrupts on all I/O pins * A dedicated 3.3V regulator for the USB PHY. Aids in signalling and D-line pull-up * 125 mA 3.3V voltage regulator can power external 3.3V devices * 3.3V I/O pins
1.1
Applications
The CY7C63310/CY7C638xx is targeted for the following applications: * PC HID devices -- Mice (optomechanical, optical, trackball) * Gaming -- Joysticks -- Game pad * General-purpose -- Barcode scanners -- POS terminal -- Consumer electronics -- Toys -- Remote controls -- Security dongles
Cypress Semiconductor Corporation Document 38-08035 Rev. *I
*
198 Champion Court
*
San Jose, CA 95134-1709 * 408-943-2600 Revised September 26, 2006
[+] Feedback
CY7C63310 CY7C638xx
2.0 Introduction
event. POR and LVD share the same interrupt. There is no separate interrupt for each. The Watchdog timer can be used to ensure the firmware never gets stalled in an infinite loop. The microcontroller supports 22 maskable interrupts in the vectored interrupt controller. Interrupt sources include a USB bus reset, LVR/POR, a programmable interval timer, a 1.024-ms output from the Free Running Timer, three USB endpoints, two capture timers, four GPIO Ports, three Port 0 pins, two SPI, a 16-bit free running timer wrap, an internal sleep timer, and a bus active interrupt. The sleep timer causes periodic interrupts when enabled. The USB endpoints interrupt after a USB transaction complete is on the bus. The capture timers interrupt whenever a new timer value is saved due to a selected GPIO edge event. A total of seven GPIO interrupts support both TTL or CMOS thresholds. For additional flexibility, on the edge sensitive GPIO pins, the interrupt polarity is programmable to be either rising or falling. The free-running 16-bit timer provides two interrupt sources: the 1.024 ms outputs and the free running counter wrap interrupt. The programmable interval timer can provide up to 1 sec resolution and provides an interrupt everytime it expires. These timers can be used to measure the duration of an event under firmware control by reading the desired timer at the start and at the end of an event, then calculating the difference between the two values. The two 8-bit capture timer registers save a programmable 8-bit range of the free-running timer when a GPIO edge occurs on the two capture pins (P0.5, P0.6). The two 8-bit captures can be ganged into a single 16-bit capture. The enCoRe II includes an integrated USB serial interface engine (SIE) that allows the chip to easily interface to a USB host. The hardware supports one USB device address with three endpoints. The USB D+ and D- pins can optionally be used as PS/2 SCLK and SDATA signals so that products can be designed to respond to either USB or PS/2 modes of operation. PS/2 operation is supported with internal 5 K pull-up resistors on P1.0 (D+) and P1.1 (D-) and an interrupt to signal the start of PS/2 activity. In USB mode, the integrated 1.5 K pull-up resistor on D- can be controlled under firmware. No external components are necessary for dual USB and PS/2 systems, and no GPIO pins need to be dedicated to switching between modes. The enCoRe II supports in-system programming by using the D+ and D- pins as the serial programming mode interface. The programming protocol is not USB.
Cypress has reinvented its leadership position in the lowspeed USB market with a new family of innovative microcontrollers. Introducing enCoRe II USB -- "enhanced Component Reduction." Cypress has leveraged its design expertise in USB solutions to advance its family of low-speed USB microcontrollers, which enable peripheral developers to design new products with a minimum number of components. The enCoRe II USB technology builds on to the enCoRe family. The enCoRe family has an integrated oscillator that eliminates the external crystal or resonator, reducing overall cost. Also integrated into this chip are other external components commonly found in low-speed USB applications such as pullup resistors, wake-up circuitry, and a 3.3V regulator. All of this reduces the overall system cost. The enCoRe II is an 8-bit Flash-programmable microcontroller with integrated low-speed USB interface. The instruction set has been optimized specifically for USB and PS/2 operations, although the microcontrollers can be used for a variety of other embedded applications. The enCoRe II features up to 20 general-purpose I/O (GPIO) pins to support USB, PS/2 and other applications. The I/O pins are grouped into four ports (Port 0 to 3). The pins on Port 0 and Port 1 may each be configured individually while the pins on Ports 2 and 3 may only be configured as a group. Each GPIO port supports high-impedance inputs, configurable pull up, open drain output, CMOS/TTL inputs, and CMOS output with up to five pins that support programmable drive strength of up to 50 mA sink current. GPIO Port 1 features four pins that interface at a voltage level of 3.3 volts. Additionally, each I/O pin can be used to generate a GPIO interrupt to the microcontroller. Each GPIO port has its own GPIO interrupt vector; in addition GPIO Port 0 has three dedicated pins that have independent interrupt vectors (P0.2 - P0.4). The enCoRe II features an internal oscillator. With the presence of USB traffic, the internal oscillator can be set to precisely tune to USB timing requirements (24 MHz 1.5%). Optionally, an external 12 MHz or 24 MHz clock can be used to provide a higher precision reference for USB operation. The clock generator provides the 12 MHz and 24 MHz clocks that remain internal to the microcontroller. The enCoRe II also has a 12-bit programmable interval timer and a 16-bit FreeRunning Timer with Capture Timer registers. In addition, the enCoRe II includes a Watchdog timer and a vectored interrupt controller The enCoRe II has up to eight Kbytes of Flash for user's code and up to 256 bytes of RAM for stack space and user variables. The Power-on reset circuit detects logic when power is applied to the device, resets the logic to a known state, and begins executing instructions at Flash address 0x0000. When power falls below a programmable trip voltage generates reset or may be configured to generate interrupt. There is a Lowvoltage detect circuit that detects when VCC drops below a programmable trip voltage. It may be configurable to generate an LVD interrupt to inform the processor about the low-voltage
3.0
Conventions
In this document, bit positions in the registers are shaded to indicate which members of the enCoRe II family implement the bits. Available in all enCoRe II family members CY7C638xx only
Document 38-08035 Rev. *I
Page 2 of 74
[+] Feedback
CY7C63310 CY7C638xx
4.0 Logic Block Diagram
Figure 4-1. CY7C63310/CY7C638xx Block Diagram
3.3V Regulator
Low-Speed USB/PS2 Transceiver and Pull-up
Low-Speed USB SIE
Interrupt Control
4 3VIO/SPI Pins
Up to 14 Extended I/O Pins
Up to 6 GPIO pins
Wakeup Timer
Internal 24 MHz Oscillator M8C CPU RAM Up to 256 Byte Flash Up to 8K Byte 16-bit Free running timer
Clock Control External Clock
12-bit Timer
POR / Low-Voltage Detect Vdd
Watchdog Timer
Document 38-08035 Rev. *I
Page 3 of 74
[+] Feedback
CY7C63310 CY7C638xx
5.0 Packages/Pinouts
Figure 5-1. Package Configurations Top View CY7C63801 16-pin PDIP CY7C63310 16-pin PDIP
SSEL/P1.3 SCLK/P1.4 SMOSI/P1.5 SMISO/P1.6 TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 1 2 3 4 5 6 7 8 16 15 14 13 12 11 10 9 P1.2 VCC P1.1/D- P1.0/D+ VSS P0.0 P0.1 P0.2/INT0
CY7C63801 16-pin SOIC CY7C63310 16-pin SOIC
TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 INT0/P0.2 P0.1 P0.0 VSS 1 2 3 4 5 6 7 8 16 15 14 13 12 11 10 9 P1.6/SMISO P1.5/SMOSI P1.4/SCLK P1.3/SSEL P1.2 VCC P1.1/D- P1.0/D+
CY7C63803 16-pin SOIC
TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 INT0/P0.2 P0.1 P0.0 VSS 1 2 3 4 5 6 7 8 16 15 14 13 12 11 10 9 P1.6/SMISO P1.5/SMOSI P1.4/SCLK P1.3/SSEL P1.2/VREG VCC P1.1/D- P1.0/D+
CY7C63813 18-pin PDIP
SSEL/P1.3 SCLK/P1.4 SMOSI/P1.5 SMISO/P1.6 P1.7 P0.7 TIO1/P0.6 TIO0/P0.5 INT2/P0.4 1 2 3 4 5 6 7 8 9 18 17 16 15 14 13 12 11 10 P1.2/VREG VCC P1.1/D- P1.0/D+ VSS P0.0 P0.1 P0.2/INT0 P0.3/INT1
CY7C63823 24-pin SOIC CY7C63813 18-pin SOIC
P0.7 TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 INT0/P0.2 P0.1 P0.0 VSS 1 2 3 4 5 6 7 8 9 18 17 16 15 14 13 12 11 10 P1.7 P1.6/SMISO P1.5/SMOSI P1.4/SCLK P1.3/SSEL P1.2/VREG VCC P1.1/D- P1.0/D+ NC P0.7 TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 INT0/P0.2 P0.1 P0.0 P2.1 P2.0 VSS 1 2 3 4 5 6 7 8 9 10 11 12 24 23 22 21 20 19 18 17 16 15 14 13 NC P1.7 P1.6/SMISO P1.5/SMOSI P1.4/SCLK P3.1 P3.0 P1.3/SSEL P1.2/VREG VCC P1.1/D- P1.0/D+
CY7C63833 32-lead QFN
P0.7 P1.7
NC
NC
NC
NC
NC P0.7 TIO1/P0.6 TIO0/P0.5 INT2/P0.4 INT1/P0.3 INT0/P0.2 P0.1 P0.0 P2.1 P2.0 NC
1 2 3 4 5 6 7 8 9 10 11 12
24 23 22 21 20 19 18 17 16 15 14 13
P1.7 P1.6/SMISO P1.5/SMOSI P1.4/SCLK P3.1 P3.0 P1.3/SSEL P1.2/VREG VCC P1.1/D- P1.0/D+ VSS
32 31 30 29 28 27 26 25 P0.6/TIO1 P0.5/TIO0 P0.4/INT2 P0.3/INT1 P0.2/INT0 P0.1 P0.0 P2.1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 P1.0/D+ P2.0 P1.1/DVss Vdd NC NC NC 24 23 22 21 20 19 18 17 P1.5/SMOSI P1.4/SCLK P3.1 P3.0 P1.3/SSEL NC P1.2/VREG NC
Document 38-08035 Rev. *I
NC
CY7C63823 24-pin QSOP
P1.6/MISO
Page 4 of 74
[+] Feedback
CY7C63310 CY7C638xx
5.1 Pinouts Assignments
Table 5-1. Pin Assignments
32 QFN 24 QSOP 24 SOIC 18 SIOC 18 PDIP 16 SOIC 16 PDIP Name Description
21 22 9 8 14
19 20 11 10 14
18 19 11 10 13 10 15 9 13
P3.0 P3.1 P2.0 P2.1 P1.0/D+
GPIO Port 3 - configured as a group (byte)
GPIO Port 2 - configured as a group (byte)
GPIO Port 1 bit 0/USB D+[1] If this pin is used as a General Purpose output, it will draw current. This pin must be configured as an input to reduce current draw. GPIO Port 1 bit 1/USB D-[1] If this pin is used as a General Purpose output, it will draw current. This pin must be configured as an input to reduce current draw.
15
15
14
11
16
10
14
P1.1/D-
18
17
16
13
18
12
16
P1.2/VREG GPIO Port 1 bit 2--Configured individually. 3.3V if regulator is enabled. (The 3.3V regulator is not available in the CY7C63310 and CY7C63801.) A 1-F min, 2-F max capacitor is required on Vreg output. P1.3/SSEL GPIO Port 1 bit 3--Configured individually. Alternate function is SSEL signal of the SPI bus TTL voltage thresholds. Although Vreg is not available with the CY7C63310, 3.3V I/O is still available. P1.4/SCLK GPIO Port 1 bit 4--Configured individually. Alternate function is SCLK signal of the SPI bus TTL voltage thresholds. Although Vreg is not available with the CY7C63310, 3.3V I/O is still available. P1.5/SMOSI GPIO Port 1 bit 5--Configured individually. Alternate function is SMOSI signal of the SPI bus TTL voltage thresholds. Although Vreg is not available with the CY7C63310, 3.3V I/O is still available. P1.6/SMISO GPIO Port 1 bit 6--Configured individually. Alternate function is SMISO signal of the SPI bus TTL voltage thresholds. Although Vreg is not available with the CY7C63310, 3.3V I/O is still available. P1.7 GPIO Port 1 bit 7--Configured individually. TTL voltage threshold. GPIO Port 0 bit 0--Configured individually. On CY7C638xx and CY7C63310, external clock input when configured as Clock In. GPIO Port 0 bit 1--Configured individually On CY7C638xx and CY7C63310, clock output when configured as Clock Out.
20
18
17
14
1
13
1
23
21
20
15
2
14
2
24
22
21
16
3
15
3
25
23
22
17
4
16
4
26 7
24 9
23 9
18 8
5 13 7 11
P0.0
6
8
8
7
12
6
10
P0.1
5 4 3
7 6 5
7 6 5
6 5 4
11 10 9
5 4 3
9 8 7
P0.2/INT0 GPIO port 0 bit 2--Configured individually Optional rising edge interrupt INT0 P0.3/INT1 GPIO port 0 bit 3--Configured individually Optional rising edge interrupt INT1 P0.4/INT2 GPIO port 0 bit 4--Configured individually Optional rising edge interrupt INT2
Note 1. P1.0(D+) and P1.1(D-) pins must be in I/O mode when used as GPIO and in Isb mode.
Document 38-08035 Rev. *I
Page 5 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 5-1. Pin Assignments (continued)
32 QFN 24 QSOP 24 SOIC 18 SIOC 18 PDIP 16 SOIC 16 PDIP Name Description
2
4
4
3
8
2
6
P0.5/TIO0 GPIO port 0 bit 5--Configured individually Alternate function Timer capture inputs or Timer output TIO0 P0.6/TIO1 GPIO port 0 bit 6--Configured individually Alternate function Timer capture inputs or Timer output TIO1 P0.7 NC NC NC NC NC NC NC NC NC NC GPIO port 0 bit 7--Configured individually Not present in the 16 pin PDIP or SOIC package No connect No connect No connect No connect No connect No connect No connect No connect No connect No connect Supply Ground
1
3
3
2
7
1
5
32 10 11 12 17 19 27 28 29 30 31 16 13
2 1 12
2 1 24
1
6
16 13
15 12
12 9
17 14
11 8
15 12
Vcc VSS
6.0
CPU Architecture
This family of microcontrollers is based on a high performance, 8-bit, Harvard-architecture microprocessor. Five registers control the primary operation of the CPU core. These registers are affected by various instructions, but are not directly accessible through the register space by the user. Table 6-1. CPU Registers and Register Names Register Flags Program Counter Accumulator Stack Pointer Index Register Name CPU_F CPU_PC CPU_A CPU_SP CPU_X
The Accumulator Register (CPU_A) is the general-purpose register that holds the results of instructions that specify any of the source addressing modes. The Index Register (CPU_X) holds an offset value that is used in the indexed addressing modes. Typically, this is used to address a block of data within the data memory space. The Stack Pointer Register (CPU_SP) holds the address of the current top-of-stack in the data memory space. It is affected by the PUSH, POP, LCALL, CALL, RETI, and RET instructions, which manage the software stack. It can also be affected by the SWAP and ADD instructions. The Flag Register (CPU_F) has three status bits: Zero Flag bit [1]; Carry Flag bit [2]; Supervisory State bit [3]. The Global Interrupt Enable bit [0] is used to globally enable or disable interrupts. The user cannot manipulate the Supervisory State status bit [3]. The flags are affected by arithmetic, logic, and shift operations. The manner in which each flag is changed is dependent upon the instruction being executed (i.e., AND, OR, XOR). See Table 8-1.
The 16-bit Program Counter Register (CPU_PC) allows for direct addressing of the full eight Kbytes of program memory space.
Document 38-08035 Rev. *I
Page 6 of 74
[+] Feedback
CY7C63310 CY7C638xx
7.0
7.1
CPU Registers
Flags Register
The Flags Register can only be set or reset with logical instruction. Table 7-1. CPU Flags Register (CPU_F) [R/W]
Bit # Field Read/Write Default - 0 7 6 Reserved - 0 - 0 5 4 XIO R/W 0 3 Super R 0 2 Carry RW 0 1 Zero RW 1 0 Global IE RW 0
Bit [7:5]: Reserved Bit 4: XIO Set by the user to select between the register banks 0 = Bank 0 1 = Bank 1 Bit 3: Super Indicates whether the CPU is executing user code or Supervisor Code. (This code cannot be accessed directly by the user) 0 = User Code 1 = Supervisor Code Bit 2: Carry Set by CPU to indicate whether there has been a carry in the previous logical/arithmetic operation 0 = No Carry 1 = Carry Bit 1: Zero Set by CPU to indicate whether there has been a zero result in the previous logical/arithmetic operation 0 = Not Equal to Zero 1 = Equal to Zero Bit 0: Global IE Determines whether all interrupts are enabled or disabled 0 = Disabled 1 = Enabled Note: CPU_F register is only readable with explicit register address 0xF7. The OR F, expr and AND F, expr instructions must be used to set and clear the CPU_F bits Table 7-2. CPU Accumulator Register (CPU_A)
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 3 2 1 0 CPU Accumulator [7:0] - 0 - 0 - 0 - 0 - 0
Bit [7:0]: CPU Accumulator [7:0] 8-bit data value holds the result of any logical/arithmetic instruction that uses a source addressing mode Table 7-3. CPU X Register (CPU_X)
Bit # Field Read/Write Default - 0 - 0 - 0 - 0 7 6 5 4 X [7:0] - 0 - 0 - 0 - 0 3 2 1 0
Bit [7:0]: X [7:0] 8-bit data value holds an index for any instruction that uses an indexed addressing mode Table 7-4. CPU Stack Pointer Register (CPU_SP)
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 3 2 1 0 Stack Pointer [7:0] - 0 - 0 - 0 - 0 - 0
Bit [7:0]: Stack Pointer [7:0] 8-bit data value holds a pointer to the current top-of-stack
Document 38-08035 Rev. *I
Page 7 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 7-5. CPU Program Counter High Register (CPU_PCH)
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 3 2 1 0 Program Counter [15:8] - 0 - 0 - 0 - 0 - 0
Bit [7:0]: Program Counter [15:8] 8-bit data value holds the higher byte of the program counter Table 7-6. CPU Program Counter Low Register (CPU_PCL)
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 4 3 2 1 0 Program Counter [7:0] - 0 - 0 - 0 - 0 - 0
Bit [7:0]: Program Counter [7:0] 8-bit data value holds the lower byte of the program counter
7.2
7.2.1
Addressing Modes
Source Immediate Examples
ADD A, [7] ;In this case, the; value in; the RAM memory location at; address 7 is added with the; Accumulator, and the result; is placed in the Accumulator. ;In this case, the value in; the register space at address; 8 is moved to the X register.
The result of an instruction using this addressing mode is placed in the A register, the F register, the SP register, or the X register, which is specified as part of the instruction opcode. Operand 1 is an immediate value that serves as a source for the instruction. Arithmetic instructions require two sources; the second one is the A or the X register specified in the opcode. Instructions using this addressing mode are two bytes in length. Table 7-7. Source Immediate Opcode Instruction Examples
ADD A, 7 ;In this case, the immediate value; of 7 is added with the Accumulator,; and the result is placed in the; Accumulator. ;In this case, the immediate value; of 8 is moved to the X register. ;In this case, the immediate value; of 9 is logically ANDed with the F; register and the result is placed; in the F register.
MOV
X,
REG[8]
Operand 1 Immediate Value
7.2.3
Source Indexed
MOV AND
X, F,
8 9
The result of an instruction using this addressing mode is placed in either the A register or the X register, which is specified as part of the instruction opcode. Operand 1 is added to the X register forming an address that points to a location in either the RAM memory space or the register space that is the source for the instruction. Arithmetic instructions require two sources; the second source is the A register or X register specified in the opcode. Instructions using this addressing mode are two bytes in length. Table 7-9. Source Indexed Opcode Instruction Examples
ADD A, [X+7] ;In this case, the value in; the memory location at; address X + 7 is added with; the Accumulator, and the; result is placed in the; Accumulator. ;In this case, the value in; the register space at; address X + 8 is moved to; the X register.
Operand 1 Source Index
7.2.2
Source Direct
The result of an instruction using this addressing mode is placed in either the A register or the X register, which is specified as part of the instruction opcode. Operand 1 is an address that points to a location in either the RAM memory space or the register space that is the source for the instruction. Arithmetic instructions require two sources; the second source is the A register or X register specified in the opcode. Instructions using this addressing mode are two bytes in length. Table 7-8. Source Direct Opcode Instruction Operand 1 Source Address
MOV
X,
REG[X+8]
Document 38-08035 Rev. *I
Page 8 of 74
[+] Feedback
CY7C63310 CY7C638xx
7.2.4 Destination Direct The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is an address that points to the location of the result. The source for the instruction is either the A register or the X register, which is specified as part of the instruction opcode. Arithmetic instructions require two sources; the second source is the location specified by Operand 1. Instructions using this addressing mode are two bytes in length. Table 7-10. Destination Direct Opcode Instruction Examples
ADD [7], A ;In this case, the value in; the memory location at; address 7 is added with the; Accumulator, and the result; is placed in the memory; location at address 7. The; Accumulator is unchanged. ;In this case, the Accumulator is moved to the register space location at address 8. The Accumulator is unchanged.
is the location specified by Operand 1. Instructions using this addressing mode are three bytes in length. Table 7-12. Destination Direct Source Immediate Opcode Instruction Examples
ADD [7], 5 ;In this case, value in the memory location at address 7 is added to the immediate value of 5, and the result is placed in the memory location at address 7. ;In this case, the immediate; value of 6 is moved into the; register space location at; address 8.
Operand 1 Destination Address
Operand 2 Immediate Value
Operand 1 Destination Address
MOV REG[8], 6
7.2.7
Destination Indexed Source Immediate
MOV
REG[8],
A
The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is added to the X register to form the address of the result. The source for the instruction is Operand 2, which is an immediate value. Arithmetic instructions require two sources; the second source is the location specified by Operand 1 added with the X register. Instructions using this addressing mode are three bytes in length. Table 7-13. Destination Indexed Source Immediate Opcode Instruction Examples
ADD [X+7], 5 ;In this case, the value in; the memory location at; address X+7 is added with; the immediate value of 5,; and the result is placed; in the memory location at; address X+7. ;In this case, the immediate value of 6 is moved; into the location in the; register space at; address X+8.
7.2.5
Destination Indexed
The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is added to the X register forming the address that points to the location of the result. The source for the instruction is the A register. Arithmetic instructions require two sources; the second source is the location specified by Operand 1 added with the X register. Instructions using this addressing mode are two bytes in length. Table 7-11. Destination Indexed Opcode Instruction Example
ADD [X+7], A ;In this case, the value in the; memory location at address X+7; is added with the Accumulator,; and the result is placed in; the memory location at address; x+7. The Accumulator is; unchanged.
Operand 1 Destination Index
Operand 2 Immediate Value
Operand 1 Destination Index
MOV REG[X+8], 6
7.2.8
Destination Direct Source Direct
7.2.6
Destination Direct Source Immediate
The result of an instruction using this addressing mode is placed within the RAM memory. Operand 1 is the address of the result. Operand 2 is an address that points to a location in the RAM memory that is the source for the instruction. This addressing mode is only valid on the MOV instruction. The instruction using this addressing mode is three bytes in length. Table 7-14. Destination Direct Source Direct Opcode Instruction Operand 1 Destination Address Operand 2 Source Address
The result of an instruction using this addressing mode is placed within either the RAM memory space or the register space. Operand 1 is the address of the result. The source for the instruction is Operand 2, which is an immediate value. Arithmetic instructions require two sources; the second source
Document 38-08035 Rev. *I
Page 9 of 74
[+] Feedback
CY7C63310 CY7C638xx
Example
MOV [7], [8] ;In this case, the value in the; memory location at address 8 is; moved to the memory location at; address 7.
7.2.10
Destination Indirect Post Increment
7.2.9
Source Indirect Post Increment
The result of an instruction using this addressing mode is placed in the Accumulator. Operand 1 is an address pointing to a location within the memory space, which contains an address (the indirect address) for the source of the instruction. The indirect address is incremented as part of the instruction execution. This addressing mode is only valid on the MVI instruction. The instruction using this addressing mode is two bytes in length. Refer to the PSoC Designer: Assembly Language User Guide for further details on MVI instruction. Table 7-15. Source Indirect Post Increment Opcode Instruction Example
MVI A, [8] ;In this case, the value in the; memory location at address 8 is an indirect address. The memory location pointed to by the indirect address is moved into the Accumulator. The indirect address is then incremented.
The result of an instruction using this addressing mode is placed within the memory space. Operand 1 is an address pointing to a location within the memory space, which contains an address (the indirect address) for the destination of the instruction. The indirect address is incremented as part of the instruction execution. The source for the instruction is the Accumulator. This addressing mode is only valid on the MVI instruction. The instruction using this addressing mode is two bytes in length. Table 7-16. Destination Indirect Post Increment Opcode Instruction Example
MVI [8], A ;In this case, the value in; the memory location at; address 8 is an indirect; address. The Accumulator is; moved into the memory location pointed to by the indirect address. The indirect; address is then incremented.
Operand 1 Destination Address Address
Operand 1 Source Address Address
Document 38-08035 Rev. *I
Page 10 of 74
[+] Feedback
CY7C63310 CY7C638xx
8.0 Instruction Set Summary
Instruction Set Summary tables are described in detail in the PSoC Designer Assembly Language User Guide (available on the www.cypress.com web site).
The instruction set is summarized in Table 8-1 numerically and serves as a quick reference. If more information is needed, the Table 8-1. Instruction Set Summary Sorted Numerically by Opcode Order[2, 3]
Opcode Hex Opcode Hex
Opcode Hex
Cycles
Cycles
Cycles
Bytes
Bytes
Instruction Format
Flags C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z Z Z Z Z Z Z Z Z Z Z Z
Instruction Format
Flags Z Z Z Z Z Z Z Z Z Z
Bytes
Instruction Format
Flags Z Z Z
00 15 01 02 03 04 05 06 08 09 0A 0B 0C 0D 0E 10 11 12 13 14 15 16 18 19 1A 1B 1C 1D 1E 20 21 22 23 24 25 26 4 6 7 7 8 9 4 4 6 7 7 8 9 4 4 6 7 7 8 9 5 4 6 7 7 8 9 5 4 6 7 7 8 9
1 SSC 2 ADD A, expr 2 ADD A, [expr] 2 ADD A, [X+expr] 2 ADD [expr], A 2 ADD [X+expr], A 3 ADD [expr], expr 3 ADD [X+expr], expr 1 PUSH A 2 ADC A, expr 2 ADC A, [expr] 2 ADC A, [X+expr] 2 ADC [expr], A 2 ADC [X+expr], A 3 ADC [expr], expr 3 ADC [X+expr], expr 1 PUSH X 2 SUB A, expr 2 SUB A, [expr] 2 SUB A, [X+expr] 2 SUB [expr], A 2 SUB [X+expr], A 3 SUB [expr], expr 3 SUB [X+expr], expr 1 POP A 2 SBB A, expr 2 SBB A, [expr] 2 SBB A, [X+expr] 2 SBB [expr], A 2 SBB [X+expr], A 3 SBB [expr], expr 3 SBB [X+expr], expr 1 POP X 2 AND A, expr 2 AND A, [expr] 2 AND A, [X+expr] 2 AND [expr], A 2 AND [X+expr], A 3 AND [expr], expr 3 AND [X+expr], expr 1 ROMX 2 OR A, expr 2 OR A, [expr] 2 OR A, [X+expr] 2 OR [expr], A
2D 2E 30 31 32 33 34 35 36 38 39 3A 3B 3C 3D
8 9 9 4 6 7 7 8 9 5 5 7 8 8 9
2 OR [X+expr], A 3 OR [expr], expr 3 OR [X+expr], expr 1 HALT 2 XOR A, expr 2 XOR A, [expr] 2 XOR A, [X+expr] 2 XOR [expr], A 2 XOR [X+expr], A 3 XOR [expr], expr 3 XOR [X+expr], expr 2 ADD SP, expr 2 CMP A, expr 2 CMP A, [expr] 2 CMP A, [X+expr] 3 CMP [expr], expr 3 CMP [X+expr], expr 2 MVI A, [ [expr]++] 2 MVI [ [expr]++], A 1 NOP 3 AND reg[expr], expr 3 AND reg[X+expr], expr 3 OR reg[expr], expr 3 OR reg[X+expr], expr 3 XOR reg[expr], expr 3 XOR reg[X+expr], expr 3 TST [expr], expr 3 TST [X+expr], expr 3 TST reg[expr], expr 3 TST reg[X+expr], expr 1 SWAP A, X 2 SWAP A, [expr] 2 SWAP X, [expr] 1 SWAP A, SP 1 MOV X, SP 2 MOV A, expr 2 MOV A, [expr] 2 MOV A, [X+expr] 2 MOV [expr], A 2 MOV [X+expr], A 3 MOV [expr], expr 3 MOV [X+expr], expr 2 MOV X, expr 2 MOV X, [expr] 2 MOV X, [X+expr]
5A 5B 5C 5D 5E 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D
5 4 4 6 7 5 6 8 9 4 7 8 4 7 8 4 7 8 4 7 8 4 4 4 4 4 4 7 8 4 4 7 8 7 8 5 5 5 5 5 7
2 MOV [expr], X 1 MOV A, X 1 MOV X, A 2 MOV A, reg[expr] 2 MOV A, reg[X+expr] 3 MOV [expr], [expr] 2 MOV reg[expr], A 2 MOV reg[X+expr], A 3 MOV reg[expr], expr 3 MOV reg[X+expr], expr 1 ASL A 2 ASL [expr] 2 ASL [X+expr] 1 ASR A 2 ASR [expr] 2 ASR [X+expr] 1 RLC A 2 RLC [expr] 2 RLC [X+expr] 1 RRC A 2 RRC [expr] 2 RRC [X+expr] 2 AND F, expr 2 OR F, expr 2 XOR F, expr 1 CPL A 1 INC A 1 INC X 2 INC [expr] 2 INC [X+expr] 1 DEC A 1 DEC X 2 DEC [expr] 2 DEC [X+expr] 3 LCALL 3 LJMP 1 RETI 1 RET 2 JMP 2 CALL 2 JZ 2 JNZ 2 JC 2 JNC 2 JACC 2 INDEX Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z C, Z
2F 10
5F 10
07 10
37 10
if (A=B) Z=1 if (A0F 10
3E 10 3F 10 40 41 43 45 47 48 49 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 4 9 9 9 8 9 9 5 7 7 5 4 4 5 6 5 6 8 9 4 6 7
Z
Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z
6E 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7D 7F 8x Ax Bx Cx Dx Ex
42 10 44 10 46 10
17 10
4A 10
1F 10
7C 13 7E 10
27 10 28 11 29 2A 2B 2C 4 6 7 7
9x 11
Fx 13
Notes 2. Interrupt routines take 13 cycles before execution resumes at interrupt vector table. 3. The number of cycles required by an instruction is increased by one for instructions that span 256-byte boundaries in the Flash memory space.
Document 38-08035 Rev. *I
Page 11 of 74
[+] Feedback
CY7C63310 CY7C638xx
9.0
9.1
Memory Organization
Flash Program Memory Organization
Figure 9-1. Program Memory Space with Interrupt Vector Table after reset 16-bit PC Address 0x0000 0x0004 0x0008 0x000C 0x0010 0x0014 0x0018 0x001C 0x0020 0x0024 0x0028 0x002C 0x0030 0x0034 0x0038 0x003C 0x0040 0x0044 0x0048 0x004C 0x0050 0x0054 0x0058 0x005C 0x0060 0x0064 0x0068 Program execution begins here after a reset POR/LVD INT0 SPI Transmitter Empty SPI Receiver Full GPIO Port 0 GPIO Port 1 INT1 EP0 EP1 EP2 USB Reset USB Active 1 ms Interval timer Programmable Interval Timer Timer Capture 0 Timer Capture 1 16-Bit Free Running Timer Wrap INT2 PS2 Data Low GPIO Port 2 GPIO Port 3 Reserved Reserved Reserved Sleep Timer Program Memory begins here (if below interrupts not used, program memory can start lower)
0x0BFF 0x0FFF
3 KB ends here (CY7C63310) 4 KB ends here (CY7C63801)
0x1FFF
8 KB ends here (CY7C638x3)
Document 38-08035 Rev. *I
Page 12 of 74
[+] Feedback
CY7C63310 CY7C638xx
9.2 Data Memory Organization
The CY7C63310/638xx microcontrollers provide up to 256 bytes of data RAM. Figure 9-2. Data Memory Organization after reset 8-bit PSP Address 0x00 Stack begins here and grows upward.
Top of RAM Memory
0xFF
9.3
Flash
use the test queue to issue Flash access functions in the SROM. The programming protocol is not USB.
This section describes the Flash block of the enCoRe II. Much of the user-visible Flash functionality including programming and security are implemented in the M8C Supervisory Read Only Memory (SROM). enCoRe II Flash has an endurance of 1000 cycles and a 10 year data retention capability. 9.3.1 Flash Programming and Security
9.4
SROM
All Flash programming is performed by code in the SROM. The registers that control the Flash programming are only visible to the M8C CPU when it is executing out of SROM. This makes it impossible to read, write or erase the Flash by bypassing the security mechanisms implemented in the SROM. Customer firmware can only program the Flash via SROM calls. The data or code images can be sourced via any interface with the appropriate support firmware. This type of programming requires a `boot-loader'--a piece of firmware resident on the Flash. For safety reasons this boot-loader must not be overwritten during firmware rewrites. The Flash provides four extra auxiliary rows that are used to hold Flash block protection flags, boot time calibration values, configuration tables, and any device values. The routines for accessing these auxiliary rows are documented in the SROM section. The auxiliary rows are not affected by the device erase function. 9.3.2 In-System Programming
The SROM holds code that is used to boot the part, calibrate circuitry, and perform Flash operations. (Table 9-1 lists the SROM functions.) The functions of the SROM may be accessed in normal user code or operating from Flash. The SROM exists in a separate memory space from user code. The SROM functions are accessed by executing the Supervisory System Call instruction (SSC), which has an opcode of 00h. Prior to executing the SSC the M8C's accumulator needs to be loaded with the desired SROM function code from Table 9-1. Undefined functions will cause a HALT if called from user code. The SROM functions are executing code with calls; therefore, the functions require stack space. With the exception of Reset, all of the SROM functions have a parameter block in SRAM that must be configured before executing the SSC. Table 9-2 lists all possible parameter block variables. The meaning of each parameter, with regards to a specific SROM function, is described later in this chapter. Table 9-1. SROM Function Codes Function Code 00h 01h 02h 03h 05h 06h 07h Function Name SWBootReset ReadBlock WriteBlock EraseBlock EraseAll TableRead CheckSum Stack Space 0 7 10 9 11 3 3
Most designs that include an enCoRe II part will have a USB connector attached to the USB D+/D- pins on the device. These designs require the ability to program or reprogram a part through these two pins alone. enCoRe II devices enable this type of in-system programming by using the D+ and D- pins as the serial programming mode interface. This allows an external controller to cause the enCoRe II part to enter serial programming mode and then to
Document 38-08035 Rev. *I
Page 13 of 74
[+] Feedback
CY7C63310 CY7C638xx
Two important variables that are used for all functions are KEY1 and KEY2. These variables are used to help discriminate between valid SSCs and inadvertent SSCs. KEY1 must always have a value of 3Ah, while KEY2 must have the same value as the stack pointer when the SROM function begins execution. This would be the Stack Pointer value when the SSC opcode is executed, plus three. If either of the keys do not match the expected values, the M8C will halt (with the exception of the SWBootReset function). The following code puts the correct value in KEY1 and KEY2. The code starts with a halt, to force the program to jump directly into the setup code and not run into it. halt SSCOP: mov [KEY1], 3ah mov X, SP mov A, X add A, 3 mov [KEY2], A Table 9-2. SROM Function Parameters Variable Name Key1/Counter/Return Code Key2/TMP BlockID Pointer Clock Mode Delay PCL 9.4.1 Return Codes SRAM Address 0,F8h 0,F9h 0,FAh 0,FBh 0,FCh 0,FDh 0,FEh 0,FFh 9.5.2 ReadBlock Function The ReadBlock function is used to read 64 contiguous bytes from Flash: a block. The first thing this function does is to check the protection bits and determine if the desired BLOCKID is readable. If read protection is turned on, the ReadBlock function will exit setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a read failure. If read protection is not enabled, the function will read 64 bytes from the Flash using a ROMX instruction and store the results in SRAM using an MVI instruction. The first of the 64 bytes will be stored in SRAM at the address indicated by the value of the POINTER parameter. When the ReadBlock completes successfully the accumulator, KEY1 and KEY2 will all have a value of 00h. Table 9-4. ReadBlock Parameters Name KEY1 KEY2 BLOCKID POINTER Address 0,F8h 0,F9h 0,FAh 0,FBh 3Ah Stack Pointer value, when SSC is executed. Flash block number First of 64 addresses in SRAM where returned data must be stored Description zeros, erase. After all the user space in all the Flash macros are erased, a second loop erases and then programs each protection block with zeros.
9.5
9.5.1
SROM Function Descriptions
SWBootReset Function
The SROM function, SWBootReset, is the function that is responsible for transitioning the device from a reset state to running user code. The SWBootReset function is executed whenever the SROM is entered with an M8C accumulator value of 00h: the SRAM parameter block is not used as an input to the function. This will happen, by design, after a hardware reset, because the M8C's accumulator is reset to 00h or when user code executes the SSC instruction with an accumulator value of 00h. The SWBootReset function will not execute when the SSC instruction is executed with a bad key value and a non-zero function code. An enCoRe II device will execute the HALT instruction if a bad value is given for either KEY1 or KEY2. The SWBootReset function verifies the integrity of the calibration data by way of a 16-bit checksum, before releasing the M8C to run user code.
The SROM also features Return Codes and Lockouts. Return codes aid in the determination of success or failure of a particular function. The return code is stored in KEY1's position in the parameter block. The CheckSum and TableRead functions do not have return codes because KEY1's position in the parameter block is used to return other data. Table 9-3. SROM Return Codes Return Code 00h 01h 02h 03h Success Function not allowed due to level of protection on block. Software reset without hardware reset. Fatal error, SROM halted. Description
9.5.3
WriteBlock Function
Read, write, and erase operations may fail if the target block is read or write protected. Block protection levels are set during device programming. The EraseAll function overwrites data in addition to leaving the entire user Flash in the erase state. The EraseAll function loops through the number of Flash macros in the product, executing the following sequence: erase, bulk program all
The WriteBlock function is used to store data in the Flash. Data is moved 64 bytes at a time from SRAM to Flash using this function. The first thing the WriteBlock function does is to check the protection bits and determine if the desired BLOCKID is writable. If write protection is turned on, the WriteBlock function will exit setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a write failure. The configuration of the WriteBlock function is straightforward. The BLOCKID of the Flash block, where the data is stored, must be determined and stored at SRAM address FAh.
Document 38-08035 Rev. *I
Page 14 of 74
[+] Feedback
CY7C63310 CY7C638xx
The SRAM address of the first of the 64 bytes to be stored in Flash must be indicated using the POINTER variable in the parameter block (SRAM address FBh). Finally, the CLOCK and DELAY value must be set correctly. The CLOCK value determines the length of the write pulse that will be used to store the data in the Flash. The CLOCK and DELAY values are dependent on the CPU speed and must be set correctly. Table 9-5. WriteBlock Parameters Name KEY1 KEY2 BLOCKID Address 0,F8h 0,F9h 0,FAh 3Ah Stack Pointer value, when SSC is executed. 8KB Flash block number (00h-7Fh) 4KB Flash block number (00h-3Fh) 3KB Flash block number (00h-2Fh) First of 64 addresses in SRAM, where the data to be stored in Flash is located prior to calling WriteBlock. Clock divider used to set the write pulse width. For a CPU speed of 12 MHz set to 56h 7 Description external reads and writes. For internal writes, IW is used. Internal reading is always permitted by way of the ROMX instruction. The ability to read by way of the SROM ReadBlock function is indicated by SR. The protection level is stored in two bits according to Table 9-7. These bits are bit packed into the 64 bytes of the protection block. Therefore, each protection block byte stores the protection level for four Flash blocks. The bits are packed into a byte, with the lowest numbered block's protection level stored in the lowest numbered bits Table 9-7. The first address of the protection block contains the protection level for blocks 0 through 3; the second address is for blocks 4 through 7. The 64th byte will store the protection level for blocks 252 through 255. Table 9-7. Protection Modes Mode 00b 01b 10b 11b Settings Description Marketing Unprotected Factory upgrade SR ER EW IW Unprotected SR ER EW IW Read protect
POINTER
0,FBh
CLOCK DELAY 9.5.4
0,FCh 0,FEh
SR ER EW IW Disable external Field upgrade write SR ER EW IW Disable internal write 6 5 4 3 2 Full protection
EraseBlock Function
1
0
The EraseBlock function is used to erase a block of 64 contiguous bytes in Flash. The first thing the EraseBlock function does is to check the protection bits and determine if the desired BLOCKID is writable. If write protection is turned on, the EraseBlock function will exit setting the accumulator and KEY2 back to 00h. KEY1 will have a value of 01h, indicating a write failure. The EraseBlock function is only useful as the first step in programming. Erasing a block will not cause data in a block to be one hundred percent unreadable. If the objective is to obliterate data in a block, the best method is to perform an EraseBlock followed by a WriteBlock of all zeros. To set up the parameter block for the EraseBlock function, correct key values must be stored in KEY1 and KEY2. The block number to be erased must be stored in the BLOCKID variable and the CLOCK and DELAY values must be set based on the current CPU speed. Table 9-6. EraseBlock Parameters Name KEY1 KEY2 BLOCKID CLOCK DELAY Address 0,F8h 0,F9h 0,FAh 0,FCh 0,FEh 3Ah Stack Pointer value, when SSC is executed. Flash block number (00h-7Fh) Clock divider used to set the erase pulse width. For a CPU speed of 12 MHz set to 56h Description
Block n+3
Block n+2
Block n+1
Block n
The level of protection is only decreased by an EraseAll, which places zeros in all locations of the protection block. To set the level of protection, the ProtectBlock function is used. This function takes data from SRAM, starting at address 80h, and ORs it with the current values in the protection block. The result of the OR operation is then stored in the protection block. The EraseBlock function does not change the protection level for a block. Because the SRAM location for the protection data is fixed and there is only one protection block per Flash macro, the ProtectBlock function expects very few variables in the parameter block to be set prior to calling the function. The parameter block values that must be set, besides the keys, are the CLOCK and DELAY values. Table 9-8. ProtectBlock Parameters Name KEY1 KEY2 CLOCK DELAY 9.5.6 Address 0,F8h 0,F9h 0,FCh 0,FEh 3Ah Stack Pointer value when SSC is executed. Clock divider used to set the write pulse width. For a CPU speed of 12 MHz set to 56h Description
EraseAll Function
9.5.5
ProtectBlock Function
The enCoRe II devices offer Flash protection on a block-byblock basis. Table 9-7 lists the protection modes available. In the table, ER and EW are used to indicate the ability to perform
The EraseAll function performs a series of steps that destroy the user data in the Flash macros and resets the protection block in each Flash macro to all zeros (the unprotected state). The EraseAll function does not affect the three hidden blocks above the protection block, in each Flash macro. The first of these four hidden blocks is used to store the protection table for its eight Kbytes of user data.
Document 38-08035 Rev. *I
Page 15 of 74
[+] Feedback
CY7C63310 CY7C638xx
The EraseAll function begins by erasing the user space of the Flash macro with the highest address range. A bulk program of all zeros is then performed on the same Flash macro, to destroy all traces of the previous contents. The bulk program is followed by a second erase that leaves the Flash macro in a state ready for writing. The erase, program, erase sequence is then performed on the next lowest Flash macro in the address space if it exists. Following the erase of the user space, the protection block for the Flash macro with the highest address range is erased. Following the erase of the protection block, zeros are written into every bit of the protection table. The next lowest Flash macro in the address space then has its protection block erased and filled with zeros. The end result of the EraseAll function is that all user data in the Flash is destroyed and the Flash is left in an unprogrammed state, ready to accept one of the various write commands. The protection bits for all user data are also reset to the zero state The parameter block values that must be set, besides the keys, are the CLOCK and DELAY values. Table 9-9. EraseAll Parameters Name KEY1 KEY2 CLOCK DELAY 9.5.7 Address 0,F8h 0,F9h 0,FCh 0,FEh 3Ah Stack Pointer value when SSC is executed. Clock divider used to set the write pulse width. For a CPU speed of 12 MHz set to 56h 9.5.8 Checksum Function The Checksum function calculates a 16-bit checksum over a user specifiable number of blocks, within a single Flash macro (Bank) starting from block zero. The BLOCKID parameter is used to pass in the number of blocks to calculate the checksum over. A BLOCKID value of 1 will calculate the checksum of only block 0, while a BLOCKID value of 0 will calculate the checksum of all 256 user blocks. The 16-bit checksum is returned in KEY1 and KEY2. The parameter KEY1 holds the lower eight bits of the checksum and the parameter KEY2 holds the upper eight bits of the checksum. The checksum algorithm executes the following sequence of three instructions over the number of blocks times 64 to be checksummed. romx add [KEY1], A adc [KEY2], 0 Table 9-11. Checksum Parameters Name The table space for the enCoRe II is simply a 64-byte row broken up into eight tables of eight bytes. The tables are numbered zero through seven. All user and hidden blocks in the CY7C638xx parts consist of 64 bytes. KEY1 KEY2 BLOCKID Address 0,F8h 0,F9h 0,FAh 3Ah Stack Pointer value when SSC is executed. Number of Flash blocks to calculate checksum on. Description Description An internal table holds the Silicon ID and returns the Revision ID. The Silicon ID is returned in SRAM, while the Revision ID is returned in the CPU_A and CPU_X registers. The Silicon ID is a value placed in the table by programming the Flash and is controlled by Cypress Semiconductor Product Engineering. The Revision ID is hard coded into the SROM. The Revision ID is discussed in more detail later in this section. An internal table holds alternate trim values for the device and returns a one-byte internal revision counter. The internal revision counter starts out with a value of zero and is incremented each time one of the other revision numbers is not incremented. It is reset to zero each time one of the other revision numbers is incremented. The internal revision count is returned in the CPU_A register. The CPU_X register will always be set to FFh when trim values are read. The BLOCKID value, in the parameter block, is used to indicate which table should be returned to the user. Only the three least significant bits of the BLOCKID parameter are used by TableRead function for the CY7C638xx. The upper five bits are ignored. When the function is called, it transfers bytes from the table to SRAM addresses F8h-FFh. The M8C's A and X registers are used by the TableRead function to return the die's Revision ID. The Revision ID is a 16-bit value hard coded into the SROM that uniquely identifies the die's design.
TableRead Function
The TableRead function gives the user access to part-specific data stored in the Flash during manufacturing. It also returns a Revision ID for the die (not to be confused with the Silicon ID). Table 9-10. Table Read Parameters Name KEY1 KEY2 Address 0,F8h 0,F9h 3Ah Stack Pointer value when SSC is executed. Table number to read. Description
BLOCKID 0,FAh
Document 38-08035 Rev. *I
Page 16 of 74
[+] Feedback
CY7C63310 CY7C638xx
10.0 Clocking
assumes the developer is interested in the lower byte of the PIT. Read_PIT_counter: mov A, reg[PITMRL] mov [57h], A mov A, reg[PITMRL] mov [58h], A mov [59h], A mov A, reg[PITMRL] mov [60h], A ;;;Start comparison mov A, [60h] mov X, [59h] sub A, [59h] jz done mov A, [59h] mov X, [58h] sub A, [58h] jz done mov X, [57h] ;;;correct data is in memory location 57h done: mov [57h], X ret
The enCoRe II internal oscillator outputs two frequencies, the Internal 24 MHz Oscillator and the 32 KHz Low-power Oscillator. The Internal 24 MHz Oscillator is designed such that it may be trimmed to an output frequency of 24 MHz over temperature and voltage variation. With the presence of USB traffic, the Internal 24 MHz Oscillator can be set to precisely tune to USB timing requirements (24 MHz 1.5%). Without USB traffic, the Internal 24 MHz Oscillator accuracy is 24 MHz 5% (between 0-70C). No external components are required to achieve this level of accuracy. The internal low-speed oscillator of nominally 32 KHz provides a slow clock source for the enCoRe II in suspend mode, particularly to generate a periodic wake-up interrupt and also to provide a clock to sequential logic during power-up and powerdown events when the main clock is stopped. In addition, this oscillator can also be used as a clocking source for the Interval Timer clock (ITMRCLK) and Capture Timer clock (TCAPCLK). The 32 KHz Low-power Oscillator can operate in low-power mode or can provide a more accurate clock in normal mode. The Internal 32 KHz Low-power Oscillator accuracy ranges (between 0-70 C) as follows: 5V Normal mode: -8% to + 16% 5V LP mode: +12% to + 48% 3.3V Normal mode: -10% to + 8% 3.3V LP mode: +4% to 35% When using the 32 KHz oscillator the PITMRL/H registers must be read until 2 consecutive readings match before sending/receiving data. The following firmware example
Document 38-08035 Rev. *I
Page 17 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 10-1. Clock Block Diagram
CPUCLK SEL
CLK_EXT MUX CLK_24MHz SCALE (divide by 2n, n = 0-5,7) CPU_CLK
EXT MUX 24 MHz CLK_USB
SEL
SCALE
SEL 0 0 1 1
SCALE X X 1 1
OUT 12 MHz 12 MHz EXT/2 EXT
LP OSC 32 KHz
CLK_32 KHz
Document 38-08035 Rev. *I
Page 18 of 74
[+] Feedback
CY7C63310 CY7C638xx
10.1 Clock Architecture Description
The enCoRe II clock selection circuitry allows the selection of independent clocks for the CPU, USB, Interval Timers and Capture Timers. The CPU clock, CPUCLK, can be sourced from an external clock or the Internal 24 MHz Oscillator. The selected clock source can optionally be divided by 2n where n is 0-5,7 (see Table 10-4). USBCLK, which must be 12 MHz for the USB SIE to function properly, can be sourced by the Internal 24 MHz Oscillator or an external 12 MHz/24 MHz clock. An optional divide by two allows the use of 24 MHz source. The Interval Timer clock (ITMRCLK), can be sourced from an external clock, the Internal 24 MHz Oscillator, the Internal 32 KHz Low-power Oscillator, or from the timer capture clock Table 10-1. IOSC Trim (IOSCTR) [0x34] [R/W]
Bit # Field Read/Write Default R/W 0 7 6 foffset[2:0] R/W 0 R/W 0 R/W D R/W D 5 4 3 2 Gain[4:0] R/W D R/W D R/W D 1 0
(TCAPCLK). A programmable prescaler of 1, 2, 3, 4 then divides the selected source. The Timer Capture clock (TCAPCLK) can be sourced from an external clock, Internal 24 MHz Oscillator, or the Internal 32 KHz Low-power Oscillator. The CLKOUT pin (P0.1) can be driven from one of many sources. This is used for test and can also be used in some applications. The sources that can drive the CLKOUT are: * CLKIN after the optional EFTB filter * Internal 24 MHz Oscillator * Internal 32 KHz Low-power Oscillator * CPUCLK after the programmable divider
The IOSC Calibrate register is used to calibrate the internal oscillator. The reset value is undefined but during boot the SROM writes a calibration value that is determined during manufacturing test. This value should not require change during normal use. This is the meaning of `D' in the Default field Bit [7:5]: foffset [2:0] This value is used to trim the frequency of the internal oscillator. These bits are not used in factory calibration and will be zero. Setting each of these bits causes the appropriate fine offset in oscillator frequency. foffset bit 0 = 7.5 KHz foffset bit 1 = 15 KHz foffset bit 2 = 30 KHz Bit [4:0]: Gain [4:0] The effective frequency change of the offset input is controlled through the gain input. A lower value of the gain setting increases the gain of the offset input. This value sets the size of each offset step for the internal oscillator. Nominal gain change (KHz/offsetStep) at each bit, typical conditions (24 MHz operation): Gain bit 0 = -1.5 KHz Gain bit 1 = -3.0 KHz Gain bit 2 = -6 KHz Gain bit 3 = -12 KHz Gain bit 4 = -24 KHz
Document 38-08035 Rev. *I
Page 19 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 10-2. LPOSC Trim (LPOSCTR) [0x36] [R/W]
Bit # Field Read/Write Default 7 32-KHz Low Power R/W 0 6 Reserved - D 5 4 3 2 1 0 32-KHz Bias Trim [1:0] R/W D R/W D R/W D 32-KHz Freq Trim [3:0] R/W D R/W D R/W D
This register is used to calibrate the 32 KHz Low-speed Oscillator. The reset value is undefined but during boot the SROM writes a calibration value that is determined during manufacturing test. This value should not require change during normal use. This is the meaning of `D' in the Default field. If the 32 KHz Low-power bit needs to be written, care must be taken not to disturb the 32 KHz Bias Trim and the 32 KHz Freq Trim fields from their factory calibrated values Bit 7: 32 KHz Low Power 0 = The 32 KHz Low-speed Oscillator operates in normal mode 1 = The 32 KHz Low-speed Oscillator operates in a low-power mode. The oscillator continues to function normally but with reduced accuracy Bit 6: Reserved Bit [5:4]: 32 KHz Bias Trim [1:0] These bits control the bias current of the low-power oscillator. 0 0 = Mid bias 0 1 = High bias 1 0 = Reserved 1 1 = Reserved Important Note: Do not program the 32 KHz Bias Trim [1:0] field with the reserved 10b value as the oscillator does not oscillate at all corner conditions with this setting Bit [3:0]: 32 KHz Freq Trim [3:0] These bits are used to trim the frequency of the low-power oscillator
Table 10-3. CPU/USB Clock Config (CPUCLKCR) [0x30] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 USB CLK/2 Disable R/W 0 5 USB CLK Select R/W 0 - 0 - 0 4 3 Reserved - 0 - 0 2 1 0 CPUCLK Select R/W 0
Bit 7: Reserved Bit 6: USB CLK/2 Disable This bit only affects the USBCLK when the source is the external crystal oscillator. When the USBCLK source is the Internal 24 MHz Oscillator, the divide by two is always enabled 0 = USBCLK source is divided by two. This is the correct setting to use when the Internal 24 MHz Oscillator is used, or when the external source is used with a 24 MHz clock 1 = USBCLK is undivided. Use this setting only with a 12 MHz external clock Bit 5: USB CLK Select This bit controls the clock source for the USB SIE 0 = Internal 24 MHz Oscillator. With the presence of USB traffic, the Internal 24 MHz Oscillator can be trimmed to meet the USB requirement of 1.5% tolerance (see Table 10-5) 1 = External clock--Internal Oscillator is not trimmed to USB traffic. Proper USB SIE operation requires a 12 MHz or 24 MHz clock accurate to <1.5%. Bit [4:1]: Reserved Bit 0: CPU CLK Select 0 = Internal 24 MHz Oscillator. 1 = External clock--External clock at CLKIN (P0.0) pin. Note: the CPU speed selection is configured using the OSC_CR0 Register (Table 10-4)
Document 38-08035 Rev. *I
Page 20 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 10-4. OSC Control 0 (OSC_CR0) [0x1E0] [R/W]
Bit # Field Read/Write Default - 0 7 Reserved - 0 6 5 No Buzz R/W 0 4 3 2 1 CPU Speed [2:0] R/W 0 R/W 0 R/W 0 0 Sleep Timer [1:0] R/W 0 R/W 0
Bit [7:6]: Reserved Bit 5: No Buzz During sleep (the Sleep bit is set in the CPU_SCR Register--Table 11-1), the LVD and POR detection circuit is turned on periodically to detect any POR and LVD events on the VCC pin (the Sleep Duty Cycle bits in the ECO_TR are used to control the duty cycle--Table 13-3). To facilitate the detection of POR and LVD events, the No Buzz bit is used to force the LVD and POR detection circuit to be continuously enabled during sleep. This results in a faster response to an LVD or POR event during sleep at the expense of a slightly higher than average sleep current 0 = The LVD and POR detection circuit is turned on periodically as configured in the Sleep Duty Cycle 1 = The Sleep Duty Cycle value is overridden. The LVD and POR detection circuit is always enabled Note: The periodic Sleep Duty Cycle enabling is independent with the sleep interval shown in the Sleep [1:0] bits below Bit [4:3]: Sleep Timer [1:0] Sleep Timer Sleep Timer Clock Sleep Period [1:0] Frequency (Nominal) (Nominal) 00 01 10 11 512 Hz 64 Hz 8 Hz 1 Hz 1.95 ms 15.6 ms 125 ms 1 sec Watchdog Period (Nominal) 6 ms 47 ms 375 ms 3 sec
Note: Sleep intervals are approximate Bit [2:0]: CPU Speed [2:0] The enCoRe II may operate over a range of CPU clock speeds. The reset value for the CPU Speed bits is zero; therefore, the default CPU speed is one-eighth of the internal 24 MHz, or 3 MHz Regardless of the CPU Speed bit's setting, if the actual CPU speed is greater than 12 MHz, the 24 MHz operating requirements apply. An example of this scenario is a device that is configured to use an external clock, which is supplying a frequency of 20 MHz. If the CPU speed register's value is 0b011, the CPU clock will be 20 MHz. Therefore the supply voltage requirements for the device are the same as if the part was operating at 24 MHz. The operating voltage requirements are not relaxed until the CPU speed is at 12 MHz or less CPU Speed [2:0] 000 001 010 011 100 101 110 111 CPU when Internal Oscillator is selected 3 MHz (Default) 6 MHz 12 MHz 24 MHz 1.5 MHz 750 KHz 187 KHz Reserved External Clock Clock In/8 Clock In/4 Clock In/2 Clock In/1 Clock In/16 Clock In/32 Clock In/128 Reserved
Important Note: Correct USB operations require the CPU clock speed be at least 1.5 MHz or not less than USB clock/8. If the two clocks have the same source then the CPU clock divider should not be set to divide by more than 8. If the two clocks have different sources, care must be taken to ensure that the maximum ratio of USB Clock/CPU Clock can never exceed 8 across the full specification range of both clock sources
Document 38-08035 Rev. *I
Page 21 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 10-5. USB Osclock Clock Configuration (OSCLCKCR) [0x39] [R/W]
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 Reserved - 0 - 0 - 0 4 3 2 1 Fine Tune Only R/W 0 0 USB Osclock Disable R/W 0
This register is used to trim the Internal 24 MHz Oscillator using received low-speed USB packets as a timing reference. The USB Osclock circuit is active when the Internal 24 MHz Oscillator provides the USB clock Bit [7:2]: Reserved Bit 1: Fine Tune Only 0 = Enable 1 = Disable the oscillator lock from performing the coarse-tune portion of its retuning. The oscillator lock must be allowed to perform a coarse tuning in order to tune the oscillator for correct USB SIE operation. After the oscillator is properly tuned this bit can be set to reduce variance in the internal oscillator frequency that would be caused course tuning Bit 0: USB Osclock Disable 0 = Enable. With the presence of USB traffic, the Internal 24 MHz Oscillator precisely tunes to 24 MHz 1.5% 1 = Disable. The Internal 24 MHz Oscillator is not trimmed based on USB packets. This setting is useful when the internal oscillator is not sourcing the USBSIE clock
Table 10-6. Timer Clock Config (TMRCLKCR) [0x31] [R/W]
Bit # Field Read/Write Default 7 6 5 4 3 2 1 0 ITMRCLK Select R/W 1 R/W 1 TCAPCLK Divider R/W 1 R/W 0 TCAPCLK Select R/W 0 R/W 0 ITMRCLK Divider R/W 1 R/W 1
Bit [7:6]: TCAPCLK Divider [1:0] TCAPCLK Divider controls the TCAPCLK divisor 0 0 = Divider Value 2 0 1 = Divider Value 4 1 0 = Divider Value 6 1 1 = Divider Value 8 Bit [5:4]: TCAPCLK Select The TCAPCLK Select field controls the source of the TCAPCLK 0 0 = Internal 24 MHz Oscillator 0 1 = External clock--external clock at CLKIN (P0.0) input. 1 0 = Internal 32-KHz Low-power Oscillator 1 1 = TCAPCLK Disabled Note: The 1024-s interval timer is based on the assumption that TCAPCLK is running at 4 MHz. Changes in TCAPCLK frequency will cause a corresponding change in the 1024-s interval timer frequency Bit [3:2]: ITMRCLK Divider ITMRCLK Divider controls the ITMRCLK divisor. 0 0 = Divider value of 1 0 1 = Divider value of 2 1 0 = Divider value of 3 1 1 = Divider value of 4 Bit [1:0]: ITMRCLK Select 0 0 = Internal 24 MHz Oscillator 0 1 = External clock--external clock at CLKIN (P0.0) input. 1 0 = Internal 32-KHz Low-power Oscillator 1 1 = TCAPCLK 10.1.1 Interval Timer Clock (ITMRCLK) unintentionally reload while the 12-bit reload value is only partially stored--i.e., between the two writes of the 12-bit value. The programmable interval timer generates an interrupt to the CPU on each reload. The parameters to be set will show up on the device editor view of PSoC Designer once you place the enCoRe II Timer User Module. The parameters are PITIMER_Source and PITIMER_Divider. The PITIMER_Source is the clock to the timer and the PITMER_Divider is the value the clock is divided by.
The Interval Timer Clock (TITMRCLK), can be sourced from an external clock, the Internal 24 MHz Oscillator, the Internal 32-KHz Low-power Oscillator, or the Timer Capture clock. A programmable prescaler of 1, 2, 3 or 4 then divides the selected source. The 12-bit Programmable Interval Timer is a simple down counter with a programmable reload value. It provides a 1 s resolution by default. When the down counter reaches zero, the next clock is spent reloading. The reload value can be read and written while the counter is running, but care must be taken to ensure that the counter does not
Document 38-08035 Rev. *I
Page 22 of 74
[+] Feedback
CY7C63310 CY7C638xx
The interval register (PITMR) holds the value that is loaded into the PIT counter on terminal count. The PIT counter is a down counter. The Programmable Interval Timer resolution is configurable. For example: TCAPCLK divide by x of CPU clock (for example TCAPCLK divide by 2 of a 24 MHz CPU clock will give a frequency of 12 MHz) ITMRCLK divide by x of TCAPCLK (for example, ITMRCLK divide by 3 of TCAPCLK is 4 MHz so resolution is 0.25 s) 10.1.2 Timer Capture Clock (TCAPCLK)
The Timer Capture clock can be sourced from an external clock, Internal 24 MHz Oscillator or the Internal 32-KHz Lowpower Oscillator. A programmable pre-scaler of 2, 4, 6, or 8 then divides the selected source.
Figure 10-2. Programmable Interval Timer Block Diagram
S y s te m C lo c k
C o n fig u ra tio n S ta tu s a n d C o n tro l
1 2 -b it re lo a d v a lu e
C lo c k T im e r
1 2 -b it d o w n c o u n te r
1 2 -b it re lo a d c o u n te r
In te rru p t C o n tro lle r
Document 38-08035 Rev. *I
Page 23 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 10-3. Timer Capture Block Diagram
System Clock
Configuration Status and C ontrol
Captim er C lock
16-bit counter
Prescale M ux
C apture Registers
1m s tim er
O verflow Interrupt Capture0 Int C apture1 Int
Interrupt Controller
Table 10-7. Clock I/O Config (CLKIOCR) [0x32] [R/W]
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 Reserved 0 0 0 4 3 2 1 CLKOUT Select R/W 0 R/W 0 0
Bit [7:2]: Reserved Bit [1:0]: CLKOUT Select 0 0 = Internal 24 MHz Oscillator 0 1 = External clock - external clock at CLKIN (P0.0) 1 0 = Internal 32-KHz Low-power Oscillator 1 1 = CPUCLK
10.2
CPU Clock During Sleep Mode
When the CPU enters sleep mode the CPUCLK Select (Bit [0], Table 10-3) is forced to the Internal Oscillator, and the oscillator is stopped. When the CPU comes out of sleep mode it is running on the internal oscillator. The internal oscillator recovery time is three clock cycles of the Internal 32-KHz Lowpower Oscillator. If the system requires the CPU to run off the external clock after awaking from sleep mode, firmware will need to switch the clock source for the CPU.
initiated, all registers are restored to their default states and all interrupts are disabled. The occurrence of a reset is recorded in the System Status and Control Register (CPU_SCR). Bits within this register record the occurrence of POR and WDR Reset respectively. The firmware can interrogate these bits to determine the cause of a reset. The microcontroller resumes execution from Flash address 0x0000 after a reset. The internal clocking mode is active after a reset, until changed by user firmware. Note The CPU clock defaults to 3 MHz (Internal 24 MHz Oscillator divide-by-8 mode) at POR to guarantee operation at the low VCC that might be present during the supply ramp.
11.0
Reset
The microcontroller supports two types of resets: Power-on Reset (POR) and Watchdog Reset (WDR). When reset is
Document 38-08035 Rev. *I
Page 24 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 11-1. System Status and Control Register (CPU_SCR) [0xFF] [R/W]
Bit # Field Read/Write Default 7 GIES R 0 6 Reserved - 0 5 WDRS R/C[4] 0 4 PORS R/C[4] 1 3 Sleep R/W 0 - 0 2 Reserved - 0 1 0 Stop R/W 0
The bits of the CPU_SCR register are used to convey status and control of events for various functions of an enCoRe II device Bit 7: GIES The Global Interrupt Enable Status bit is a read only status bit and its use is discouraged. The GIES bit is a legacy bit, which was used to provide the ability to read the GIE bit of the CPU_F register. However, the CPU_F register is now readable. When this bit is set, it indicates that the GIE bit in the CPU_F register is also set which, in turn, indicates that the microprocessor will service interrupts 0 = Global interrupts disabled 1 = Global interrupt enabled Bit 6: Reserved Bit 5: WDRS The WDRS bit is set by the CPU to indicate that a WDR event has occurred. The user can read this bit to determine the type of reset that has occurred. The user can clear but not set this bit 0 = No WDR 1 = A WDR event has occurred Bit 4: PORS The PORS bit is set by the CPU to indicate that a POR event has occurred. The user can read this bit to determine the type of reset that has occurred. The user can clear but not set this bit 0 = No POR 1 = A POR event has occurred. (Note that WDR events will not occur until this bit is cleared) Bit 3: SLEEP Set by the user to enable CPU sleep state. CPU will remain in sleep mode until any interrupt is pending. The Sleep bit is covered in more detail in the Sleep Mode section 0 = Normal operation 1 = Sleep Bit [2:1]: Reserved Bit 0: STOP This bit is set by the user to halt the CPU. The CPU will remain halted until a reset (WDR, POR, or external reset) has taken place. If an application wants to stop code execution until a reset, the preferred method would be to use the HALT instruction rather than writing to this bit 0 = Normal CPU operation 1 = CPU is halted (not recommended)
11.1
Power-on Reset
POR occurs every time the power to the device is switched on. POR is released when the supply is typically 2.6V for the upward supply transition, with typically 50 mV of hysteresis during the power-on transient. Bit 4 of the System Status and Control Register (CPU_SCR) is set to record this event (the register contents are set to 00010000 by the POR). After a POR, the microprocessor is held off for approximately 20 ms for the VCC supply to stabilize before executing the first instruction at address 0x00 in the Flash. If the VCC voltage drops below the POR downward supply trip point, POR is reasserted. The VCC supply needs to ramp linearly from 0 to 4V in less than 200 ms. Important: The PORS status bit is set at POR and can only be cleared by the user. It cannot be set by firmware.
cleared, the WDT cannot be disabled. The only exception to this is if a POR event takes place, which will disable the WDT. The sleep timer is used to generate the sleep time period and the Watchdog time period. The sleep timer uses the Internal 32-KHz Low-power Oscillator system clock to produce the sleep time period. The user can program the sleep time period using the Sleep Timer bits of the OSC_CR0 Register (Table 10-4). When the sleep time elapses (sleep timer overflows), an interrupt to the Sleep Timer Interrupt Vector will be generated. The Watchdog Timer period is automatically set to be three counts of the Sleep Timer overflows. This represents between two and three sleep intervals depending on the count in the Sleep Timer at the previous WDT clear. When this timer reaches three, a WDR is generated. The user can either clear the WDT, or the WDT and the Sleep Timer. Whenever the user writes to the Reset WDT Register (RES_WDT), the WDT will be cleared. If the data that is written is the hex value 0x38, the Sleep Timer will also be cleared at the same time.
11.2
Watchdog Timer Reset
The user has the option to enable the WDT. The WDT is enabled by clearing the PORS bit. Once the PORS bit is
Note 4. C = Clear. This bit can only be cleared by the user and cannot be set by firmware.
Document 38-08035 Rev. *I
Page 25 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 11-2. Reset Watchdog Timer (RESWDT) [0xE3] [W]
Bit # Field Read/Write Default W 0 W 0 W 0 7 6 5 4 3 2 1 0 Reset Watchdog Timer [7:0] W 0 W 0 W 0 W 0 W 0
Any write to this register will clear Watchdog Timer, a write of 0x38 will also clear the Sleep Timer Bit [7:0]: Reset Watchdog Timer [7:0]
12.0
Sleep Mode
The CPU can only be put to sleep by the firmware. This is accomplished by setting the Sleep bit in the System Status and Control Register (CPU_SCR). This stops the CPU from executing instructions, and the CPU will remain asleep until an interrupt comes pending, or there is a reset event (either a Power-on Reset, or a Watchdog Timer Reset). The Low-voltage Detection circuit (LVD) drops into fully functional power-reduced states, and the latency for the LVD is increased. The actual latency can be traded against power consumption by changing Sleep Duty Cycle field of the ECO_TR Register. The Internal 32 KHz Low-speed Oscillator remains running. Prior to entering suspend mode, firmware can optionally configure the 32 KHz Low-speed Oscillator to operate in a lowpower mode to help reduce the over all power consumption (Using Bit 7, Table 10-2). This will help save approximately 5 A; however, the trade off is that the 32 KHz Low-speed Oscillator will be less accurate. All interrupts remain active. Only the occurrence of an interrupt will wake the part from sleep. The Stop bit in the System Status and Control Register (CPU_SCR) must be cleared for a part to resume out of sleep. The Global Interrupt Enable bit of the CPU Flags Register (CPU_F) does not have any effect. Any unmasked interrupt will wake the system up. As a result, any interrupts not intended for waking must be disabled through the Interrupt Mask Registers. When the CPU enters sleep mode the CPUCLK Select (Bit 1, Table 10-3) is forced to the Internal Oscillator. The internal oscillator recovery time is three clock cycles of the Internal 32 KHz Low-power Oscillator. The Internal 24 MHz Oscillator restarts immediately on exiting Sleep mode. If an external clock is used, firmware will need to switch the clock source for the CPU. On exiting sleep mode, once the clock is stable and the delay time has expired, the instruction immediately following the sleep instruction is executed before the interrupt service routine (if enabled).
The Sleep interrupt allows the microcontroller to wake up periodically and poll system components while maintaining very low average power consumption. The Sleep interrupt may also be used to provide periodic interrupts during nonsleep modes.
12.1
Sleep Sequence
The SLEEP bit is an input into the sleep logic circuit. This circuit is designed to sequence the device into and out of the hardware sleep state. The hardware sequence to put the device to sleep is shown in Figure 12-1 and is defined as follows. 1.Firmware sets the SLEEP bit in the CPU_SCR0 register. The Bus Request (BRQ) signal to the CPU is immediately asserted. This is a request by the system to halt CPU operation at an instruction boundary. The CPU samples BRQ on the positive edge of CPUCLK. 2.Due to the specific timing of the register write, the CPU issues a Bus Request Acknowledge (BRA) on the following positive edge of the CPU clock. The sleep logic waits for the following negative edge of the CPU clock and then asserts a system-wide Power Down (PD) signal. In Figure 12-1 the CPU is halted and the system-wide power down signal is asserted. 3. The system-wide PD (power down) signal controls several major circuit blocks: The Flash memory module, the internal 24 MHz oscillator, the EFTB filter and the bandgap voltage reference. These circuits transition into a zero power state. The only operational circuits on chip are the Low Power oscillator, the bandgap refresh circuit, and the supply voltage monitor (POR/LVD) circuit. Note: To achieve the lowest possible power consumption during suspend/sleep, the following conditions must be observed in addition to considerations for the sleep timer: * All GPIOs must be set to outputs and driven low * The USB pins P1.0 and P1.1 should be configured as inputs with their pull-ups enabled.
Document 38-08035 Rev. *I
Page 26 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 12-1. Sleep Timing
Firmware write to SCR SLEEP bit causes an immediate BRQ
CPU captures BRQ on next CPUCLK edge
CPU responds with a BRA
On the falling edge of CPUCLK, PD is asserted. The 24/48 MHz system clock is halted; the Flash and bandgap are powered down
CPUCLK IOW SLEEP BRQ BRA PD
12.2
Wake up Sequence
Once asleep, the only event that can wake the system up is an interrupt. The global interrupt enable of the CPU flag register does not need to be set. Any unmasked interrupt will wake the system up. It is optional for the CPU to actually take the interrupt after the wake up sequence. The wake up sequence is synchronized to the 32 kHz clock for purposes of sequencing a startup delay, to allow the Flash memory module enough time to power up before the CPU asserts the first read access. Another reason for the delay is to allow the oscillator, Bandgap, and LVD/POR circuits time to settle before actually being used in the system. As shown in Figure 12-2, the wake up sequence is as follows: 1.The wake up interrupt occurs and is synchronized by the negative edge of the 32 kHz clock.
2.At the following positive edge of the 32 kHz clock, the system wide PD signal is negated. The Flash memory module, internal oscillator, EFTB, and bandgap circuit are all powered up to a normal operating state. 3.At the following positive edge of the 32 kHz clock, the current values for the precision POR and LVD have settled and are sampled. 4.At the following negative edge of the 32 kHz clock (after about 15 S nominal), the BRQ signal is negated by the sleep logic circuit. On the following CPUCLK, BRA is negated by the CPU and instruction execution resumes. Note that in Figure 12-2 fixed function blocks, such as Flash, internal oscillator, EFTB, and bandgap, have about 15 Sec start up. The wake-up times (interrupt to CPU operational) will range from 75 S to 105 S.
Document 38-08035 Rev. *I
Page 27 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 12-2. Wake up Timing
Sleep Timer or GPIO interrupt occurs
Interrupt is double sampled by 32K clock and PD is negated to system
CPU is restarted after 90ms (nominal)
CLK32K INT SLEEP PD BANDGAP LVD PPOR ENABLE SAMPLE SAMPLE LVD/POR CPUCLK/ 24MHz (Not to Scale) BRQ BRA CPU
Document 38-08035 Rev. *I
Page 28 of 74
[+] Feedback
CY7C63310 CY7C638xx
13.0 Low-voltage Detect Control
Table 13-1. Low-voltage Control Register (LVDCR) [0x1E3] [R/W]
Bit # Field Read/Write Default - 0 7 Reserved - 0 R/W 0 6 5 PORLEV[1:0] R/W 0 4 3 Reserved - 0 R/W 0 2 1 VM[2:0] R/W 0 R/W 0 0
This register controls the configuration of the Power-on Reset/Low-voltage Detection block Bit [7:6]: Reserved Bit [5:4]: PORLEV[1:0] This field controls the level below which the precision power-on-reset (PPOR) detector generates a reset 0 0 = 2.7V Range (trip near 2.6V) 0 1 = 3V Range (trip near 2.9V) 1 0 = 5V Range, >4.75V (trip near 4.65V) 1 1 = PPOR will not generate a reset, but values read from the Voltage Monitor Comparators Register (Table 13-2) give the internal PPOR comparator state with trip point set to the 3V range setting Bit 3: Reserved Bit [2:0]: VM[2:0] This field controls the level below which the low-voltage-detect trips--possibly generating an interrupt and the level at which the Flash is enabled for operation. VM[2:0] 000 001 010 011 100 101 110 111 LVD Trip Point LVD Trip LVD Trip Point (V) Min (V) Max Point (V) Typ 2.681 2.892 2.991 3.102 4.439 4.597 4.680 4.766 2.70 2.92 3.02 3.13 4.48 4.64 4.73 4.82 2.735 2.950 3.053 3.164 4.528 4.689 4.774 4.862
Table 13-2. Voltage Monitor Comparators Register (VLTCMP) [0x1E4] [R]
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 Reserved - 0 - 0 - 0 4 3 2 1 LVD R 0 0 PPOR R 0
This read-only register allows reading the current state of the Low-voltage-Detection and Precision-Power-On-Reset comparators Bit [7:2]: Reserved Bit 1: LVD This bit is set to indicate that the low-voltage-detect comparator has tripped, indicating that the supply voltage has gone below the trip point set by VM[2:0] (See Table 13-1) 0 = No low-voltage-detect event 1 = A low-voltage-detect has tripped Bit 0: PPOR This bit is set to indicate that the precision-power-on-reset comparator has tripped, indicating that the supply voltage is below the trip point set by PORLEV[1:0] 0 = No precision-power-on-reset event 1 = A precision-power-on-reset event has occurred Note: This register can only be accessed in the second bank of I/O space. This requires setting the XIO bit in the CPU flags register.
Document 38-08035 Rev. *I
Page 29 of 74
[+] Feedback
CY7C63310 CY7C638xx
13.0.1 ECO Trim Register
Table 13-3. ECO (ECO_TR) [0x1EB] [R/W]
Bit # Field Read/Write Default 7 6 5 4 3 Reserved - 0 - 0 - 0 - 0 - 0 - 0 2 1 0
Sleep Duty Cycle [1:0] R/W 0 R/W 0
This register controls the ratios (in numbers of 32-KHz clock periods) of "on" time versus "off" time for LVD and POR detection circuit Bit [7:6]: Sleep Duty Cycle [1:0] 0 0 = 128 periods of the Internal 32 KHz Low-speed Oscillator 0 1 = 512 periods of the Internal 32 KHz Low-speed Oscillator 1 0 = 32 periods of the Internal 32 KHz Low-speed Oscillator 1 1 = 8 periods of the Internal 32 KHz Low-speed Oscillator
14.0
14.1
General-purpose I/O Ports
Port Data Registers
Table 14-1. P0 Data Register (P0DATA)[0x00] [R/W]
Bit # Field Read/Write Default 7 P0.7 R/W 0 6 P0.6/TIO1 R/W 0 5 P0.5/TIO0 R/W 0 4 P0.4/INT2 R/W 0 3 P0.3/INT1 R/W 0 2 P0.2/INT0 R/W 0 1 P0.1/CLKOUT R/W 0 0 P0.0/CLKIN R/W 0
This register contains the data for Port 0. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 0 pins. Bit 7: P0.7 Data P0.7 only exists in the CY7C638xx Bit [6:5]: P0.6-P0.5 Data/TIO1 and TIO0 Beside their use as the P0.6-P0.5 GPIOs, these pins can also be used for the alternate functions as the Capture Timer input or Timer output pins (TIO1 and TIO0). To configure the P0.5 and P0.6 pins, refer to the P0.5/TIO0-P0.6/TIO1 Configuration Register (Table 14-8) The use of the pins as the P0.6-P0.5 GPIOs and the alternate functions exist in all the enCoRe II parts Bit [4:2]: P0.4-P0.2 Data/INT2 - INT0 Beside their use as the P0.4-P0.2 GPIOs, these pins can also be used for the alternate functions as the Interrupt pins (INT0-INT2). To configure the P0.4-P0.2 pins, refer to the P0.2/INT0-P0.4/INT2 Configuration Register (Table 14-7) The use of the pins as the P0.4-P0.2 GPIOs and the alternate functions exist in all the enCoRe II parts Bit 1: P0.1/CLKOUT Beside its use as the P0.1 GPIO, this pin can also be used for the alternate function as the CLK OUT pin. To configure the P0.1 pin, refer to the P0.1/CLKOUT Configuration Register (Table 14-6) Bit 0: P0.0/CLKIN Beside its use as the P0.0 GPIO, this pin can also be used for the alternate function as the CLKIN pin. To configure the P0.0 pin, refer to the P0.0/CLKIN Configuration Register (Table 14-5)
Document 38-08035 Rev. *I
Page 30 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 14-2. P1 Data Register (P1DATA) [0x01] [R/W]
Bit # Field Read/Write Default 7 P1.7 R/W 0 6 P1.6/SMISO R/W 0 5 P1.5/SMOSI R/W 0 4 P1.4/SCLK R/W 0 3 P1.3/SSEL R/W 0 2 P1.2/VREG R/W 0 1 P1.1/D- R/W 0 0 P1.0/D+ R/W 0
This register contains the data for Port 1. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 1 pins. Bit 7: P1.7 Data P1.7 only exists in the CY7C638xx Bit [6:3]: P1.6-P1.3 Data/SPI Pins (SMISO, SMOSI, SCLK, SSEL) Beside their use as the P1.6-P1.3 GPIOs, these pins can also be used for the alternate function as the SPI interface pins. To configure the P1.6-P1.3 pins, refer to the P1.3-P1.6 Configuration Register (Table 14-13) The use of the pins as the P1.6-P1.3 GPIOs and the alternate functions exist in all the enCoRe II parts. Bit 2: P1.2/VREG On the CY7C638(2/3)3, this pin can be used as the P1.2 GPIO or the VREG output. If the VREG output is enabled (Bit 0 Table 19-1 is set), a 3.3V source is placed on the pin and the GPIO function of the pin is disabled On the CY7C63813, this pin can only be used as the VREG output when USB mode is enabled. In non-USB mode, this pin can be used as the P1.2 GPIO. The VREG functionality is not present in the CY7C63310 and the CY7C63801 variants. A 1 F min, 2 F max capacitor is required on VREG output. Bit [1:0]: P1.1-P1.0/D- and D+ When USB mode is disabled (Bit 7 in Table 21-1 is clear), the P1.1 and P1.0 bits are used to control the state of the P1.0 and P1.1 pins. When the USB mode is enabled, the P1.1 and P1.0 pins are used as the D- and D+ pins respectively. If the USB Force State bit (Bit 0 in Table 18-1) is set, the state of the D- and D+ pins can be controlled by writing to the D- and D+ bits
Table 14-3. P2 Data Register (P2DATA) [0x02] [R/W]
Bit # Field Read/Write Default 0 0 0 7 6 5 Reserved 0 0 0 R/W 0 4 3 2 1 P2.1-P2.0 R/W 0 0
This register contains the data for Port 2. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 2 pins Bit [7:2]: Reserved Data [7:2] Bit [1:0]: P2 Data [1:0] P2.1-P2.0 only exist in the CY7C638(2/3)3
Table 14-4. P3 Data Register (P3DATA) [0x03] [R/W]
Bit # Field Read/Write Default 0 0 0 7 6 5 Reserved 0 0 0 R/W 0 4 3 2 1 P3.1-P3.0 R/W 0 0
This register contains the data for Port 3. Writing to this register sets the bit values to be output on output enabled pins. Reading from this register returns the current state of the Port 3 pins Bit [7:2]: Reserved Data [7:2] Bit [1:0]: P3 Data [1:0] P3.1-P3.0 only exist in the CY7C638(2/3)3
14.2
GPIO Port Configuration
All the GPIO configuration registers have common configuration controls. The following are the bit definitions of the GPIO configuration registers 14.2.1 Int Enable
sensitive, however for any interrupt that is shared by multiple sources (i.e., Ports 2, 3, and 4) all inputs must be deasserted before a new interrupt can occur. When clear, the corresponding interrupt is disabled on the pin. It is possible to configure GPIOs as outputs, enable the interrupt on the pin and then to generate the interrupt by driving the appropriate pin state. This is useful in test and may have value in applications as well.
When set, the Int Enable bit allows the GPIO to generate interrupts. Interrupt generate can occur regardless of whether the pin is configured for input or output. All interrupts are edge
Document 38-08035 Rev. *I
Page 31 of 74
[+] Feedback
CY7C63310 CY7C638xx
14.2.2 Int Act Low When clear, the pull up is disabled. 14.2.7 Output Enable When set, the corresponding interrupt is active on the falling edge. When clear, the corresponding interrupt is active on the rising edge. 14.2.3 TTL Thresh
When set, the output driver of the pin is enabled. When clear, the output driver of the pin is disabled. For pins with shared functions there are some special cases. 14.2.8 VREG Output/SPI Use
When set, the input has TTL threshold. When clear, the input has standard CMOS threshold. 14.2.4 High Sink
The P1.2(VREG), P1.3(SSEL), P1.4(SCLK), P1.5(SMOSI) and P1.6(SMISO) pins can be used for their dedicated functions or for GPIO. To enable the pin for GPIO, clear the corresponding VREG Output or SPI Use bit. The SPI function controls the output enable for its dedicated function pins when their GPIO enable bit is clear. The VREG output is not available on the CY7C63801 and CY7C63310. 14.2.9 3.3V Drive
When set, the output can sink up to 50 mA. When clear, the output can sink up to 8 mA. On the CY7C638xx, only the P1.7-P1.3 have 50 mA sink drive capability. Other pins have 8 mA sink drive capability. 14.2.5 Open Drain
When set, the output on the pin is determined by the Port Data Register. If the corresponding bit in the Port Data Register is set, the pin is in high-impedance state. If the corresponding bit in the Port Data Register is clear, the pin is driven low. When clear, the output is driven LOW or HIGH. 14.2.6 Pull up Enable
The P1.3(SSEL), P1.4(SCLK), P1.5(SMOSI) and P1.6(SMISO) pins have an alternate voltage source from the voltage regulator. If the 3.3V Drive bit is set a high level is driven from the voltage regulator instead of from VCC. Setting the 3.3V Drive bit does not enable the voltage regulator. That must be done explicitly by setting the VREG Enable bit in the VREGCR Register (Table 19-1).
When set the pin has a 7K pull up to VCC (or VREG for ports with V3.3 enabled). Figure 14-1. Block Diagram of a GPIO
VE RG 3 VD e .3 riv
VC C
P ll-U E a le u p nb O tp t E a le u u nb VE RG O e D in p n ra P rt D ta oa VC C RP U D taO t au G IO P P IN
H hS k ig in
VE GD RG N D taIn a T LT re h ld T h so
V CG D N C
Document 38-08035 Rev. *I
Page 32 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 14-5. P0.0/CLKIN Configuration (P00CR) [0x05] [R/W]
Bit # Field Read/Write Default 7 Reserved -0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This pin is shared between the P0.0 GPIO use and the CLKIN pin for an external clock. When the external clock input is enabled the settings of this register are ignored The use of the pin as the P0.0 GPIO is available in all the enCoRe II parts. In the CY7C638xx, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit
Table 14-6. P0.1/CLKOUT Configuration (P01CR) [0x06] R/W]
Bit # Field Read/Write Default 7 CLK Output R/W 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This pin is shared between the P0.1 GPIO use and the CLKOUT pin. When CLK output is set, the internally selected clock is sent out onto P0.1CLKOUT pin. The use of the pin as the P0.1 GPIO is available in all the enCoRe II parts. In the CY7C638xx, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit Bit 7: CLK Output 0 = The clock output is disabled 1 = The clock selected by the CLK Select field (Bit [1:0] of the CLKIOCR Register--Table 10-7) is driven out to the pin
Table 14-7. P0.2/INT0-P0.4/INT2 Configuration (P02CR-P04CR) [0x07-0x09] [R/W]
Bit # Field Read/Write Default - 0 7 Reserved - 0 6 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 Reserved - 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
These registers control the operation of pins P0.2-P0.4 respectively. These pins are shared between the P0.2-P0.4 GPIOs and the INT0-INT2. These registers exist in all enCoRe II parts. The INT0-INT2 interrupts are different than all the other GPIO interrupts. These pins are connected directly to the interrupt controller to provide three edge-sensitive interrupts with independent interrupt vectors. These interrupts occur on a rising edge when Int act Low is clear and on a falling edge when Int act Low is set. These pins are enabled as interrupt sources in the interrupt controller registers (Table 17-8 and Table 17-6). To use these pins as interrupt inputs configure them as inputs by clearing the corresponding Output Enable. If the INT0-INT2 pins are configured as outputs with interrupts enabled, firmware can generate an interrupt by writing the appropriate value to the P0.2, P0.3 and P0.4 data bits in the P0 Data Register Regardless of whether the pins are used as Interrupt or GPIO pins the Int Enable, Int act Low, TTL Threshold, Open Drain, and Pull-up Enable bits control the behavior of the pin The P0.2/INT0-P0.4/INT2 pins are individually configured with the P02CR (0x07), P03CR (0x08), and P04CR (0x09) respectively. Note: Changing the state of the Int Act Low bit can cause an unintentional interrupt to be generated. When configuring these interrupt sources, it is best to follow the following procedure: 1. Disable interrupt source 2. Configure interrupt source 3. Clear any pending interrupts from the source 4. Enable interrupt source
Document 38-08035 Rev. *I
Page 33 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 14-8. P0.5/TIO0 - P0.6/TIO1 Configuration (P05CR-P06CR) [0x0A-0x0B] [R/W]
Bit # Field Read/Write Default 7 TIO Output - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 Reserved - 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
These registers control the operation of pins P0.5 through P0.6, respectively. These registers exist in all enCoRe II parts. P0.5 and P0.6 are shared with TIO0 and TIO1, respectively. To use these pins as Capture Timer inputs, configure them as inputs by clearing the corresponding Output Enable. To use TIO0 and TIO1 as Timer outputs, set the TIOx Output and Output Enable bits. If these pins are configured as outputs and the TIO Output bit is clear, firmware can control the TIO0 and TIO1 inputs by writing the value to the P0.5 and P0.6 data bits in the P0 Data Register Regardless of whether either pin is used as a TIO or GPIO pin the Int Enable, Int act Low, TTL Threshold, Open Drain, and Pullup Enable control the behavior of the pin. TIO0(P0.5) when enabled outputs a positive pulse from the 1024-s interval timer. This is the same signal that is used internally to generate the 1024-s timer interrupt. This signal is not gated by the interrupt enable state. TIO1(P0.6) when enabled outputs a positive pulse from the programmable interval timer. This is the same signal that is used internally to generate the programmable timer interval interrupt. This signal is not gated by the interrupt enable state The P0.5/TIO0 and P0.6/TIO1 pins are individually configured with the P05CR (0x0A) and P06CR (0x0B), respectively
Table 14-9. P0.7 Configuration (P07CR) [0x0C] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 Reserved - 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This register controls the operation of pin P0.7. The P0.7 pin only exists in the CY7C638(2/3)3
Table 14-10. P1.0/D+ Configuration (P10CR) [0x0D] [R/W]
Bit # Field Read/Write Default 7 Reserved R/W 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 - 0 4 3 Reserved - 0 - 0 2 1 PS/2 Pull-up Enable R/W 0 0 Output Enable R/W 0
This register controls the operation of the P1.0 (D+) pin when the USB interface is not enabled, allowing the pin to be used as a PS2 interface or a GPIO. See Table 21-1 for information on enabling USB. When USB is enabled, none of the controls in this register have any affect on the P1.0 pin. Note: The P1.0 is an open drain only output. It can actively drive a signal low, but cannot actively drive a signal high. Bit 1: PS/2 Pull-up Enable 0 = Disable the 5K ohm pull-up resistors 1 = Enable 5K ohm pull-up resistors for both P1.0 and P1.1. Enable the use of the P1.0 (D+) and P1.1 (D-) pins as a PS2 style interface
Table 14-11. P1.1/D- Configuration (P11CR) [0x0E] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 - 0 4 Reserved - 0 3 2 Open Drain R/W 0 1 Reserved - 0 0 Output Enable R/W 0
This register controls the operation of the P1.1 (D-) pin when the USB interface is not enabled, allowing the pin to be used as a PS2 interface or a GPIO. See Table 21-1 for information on enabling USB. When USB is enabled, none of the controls in this register have any affect on the P1.1 pin. When USB is disabled, the 5K ohm pull-up resistor on this pin can be enabled by the PS/2 Pull-up Enable bit of the P10CR Register (Table 14-10) Note: There is no 2 mA sourcing capability on this pin. The pin can only sink 5 mA at VOL3 (Section 26.0)
Document 38-08035 Rev. *I
Page 34 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 14-12. P1.2 Configuration (P12CR) [0x0F] [R/W]
Bit # Field Read/Write Default 7 CLK Output R/W 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Threshold R/W 0 3 Reserved - 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This register controls the operation of the P1.2 Bit 7: CLK Output 0 = The internally selected clock is not sent out onto P1.2 pin 1 = When CLK Output is set, the internally selected clock is sent out onto P1.2 pin
Table 14-13. P1.3 Configuration (P13CR) [0x10] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 3.3V Drive R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This register controls the operation of the P1.3 pin. This register exists in all enCoRe II parts The P1.3 GPIO's threshold is always set to TTL When the SPI hardware is enabled, the output enable and output state of the pin is controlled by the SPI circuitry. When the SPI hardware is disabled, the pin is controlled by the Output Enable bit and the corresponding bit in the P1 data register. Regardless of whether the pin is used as an SPI or GPIO pin the Int Enable, Int act Low, 3.3V Drive, High Sink, Open Drain, and Pull-up Enable control the behavior of the pin The 50 mA sink drive capability is only available in the CY7C638xx.
Table 14-14. P1.4-P1.6 Configuration (P14CR-P16CR) [0x11-0x13] [R/W]
Bit # Field Read/Write Default 7 SPI Use R/W 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 3.3V Drive R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
These registers control the operation of pins P1.4-P1.6, respectively. These registers exist in all enCoRe II parts The P1.4-P1.6 GPIO's threshold is always set to TTL When the SPI hardware is enabled, pins that are configured as SPI Use have their output enable and output state controlled by the SPI circuitry. When the SPI hardware is disabled or a pin has its SPI Use bit clear, the pin is controlled by the Output Enable bit and the corresponding bit in the P1 data register. Regardless of whether any pin is used as an SPI or GPIO pin the Int Enable, Int act Low, 3.3V Drive, High Sink, Open Drain, and Pull-up Enable control the behavior of the pin The 50 mA sink drive capability is only available in the CY7C638xx. Bit 7: SPI Use 0 = Disable the SPI alternate function. The pin is used as a GPIO 1 = Enable the SPI function. The SPI circuitry controls the output of the pin Important Note for Comm Modes 01 or 10 (SPI Master or SPI Slave, see Table 15-2): When configured for SPI (SPI Use = 1 and Comm Modes [1:0] = SPI Master or SPI Slave mode), the input/output direction of pins P1.3, P1.5, and P1.6 is set automatically by the SPI logic. However, pin P1.4's input/output direction is NOT automatically set; it must be explicitly set by firmware. For SPI Master mode, pin P1.4 must be configured as an output; for SPI Slave mode, pin P1.4 must be configured as an input.
Table 14-15. P1.7 Configuration (P17CR) [0x14] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 1 0 Output Enable R/W 0
This register controls the operation of pin P1.7. This register only exists in CY7C638xx The 50 mA sink drive capability is only available in the CY7C638xx. The P1.7 GPIO's threshold is always set to TTL
Document 38-08035 Rev. *I
Page 35 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 14-16. P2 Configuration (P2CR) [0x15] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 0 0 Output Enable R/W 0
This register only exists in CY7C638xx. This register controls the operation of pins P2.0-P2.1. In the CY7C638xx, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit
Table 14-17. P3 Configuration (P3CR) [0x16] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Int Enable R/W 0 5 Int Act Low R/W 0 4 TTL Thresh R/W 0 3 High Sink R/W 0 2 Open Drain R/W 0 1 Pull-up Enable R/W 1 0 Output Enable R/W 0
This register exists in CY7C638xx. This register controls the operation of pins P3.0-P3.1. In the CY7C638xx, only 8 mA sink drive capability is available on this pin regardless of the setting of the High Sink bit
15.0
Serial Peripheral Interface (SPI)
The SPI Master/Slave Interface core logic runs on the SPI clock domain, making its functionality independent of system clock speed. SPI is a four pin serial interface comprised of a clock, an enable and two data pins.
15.1
SPI Data Register
Table 15-1. SPI Data Register (SPIDATA) [0x3C] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 R/W 0 7 6 5 4 SPIData[7:0] R/W 0 R/W 0 R/W 0 R/W 0 3 2 1 0
When read, this register returns the contents of the receive buffer. When written, it loads the transmit holding register Bit [7:0]: SPI Data [7:0] When an interrupt occurs to indicate to firmware that a byte of receive data is available, or the transmitter holding register is empty, firmware has 7 SPI clocks to manage the buffers--to empty the receiver buffer, or to refill the transmit holding register. Failure to meet this timing requirement will result in incorrect data transfer.
Document 38-08035 Rev. *I
Page 36 of 74
[+] Feedback
CY7C63310 CY7C638xx
15.2 SPI Configure Register
Table 15-2. SPI Configure Register (SPICR) [0x3D] [R/W]
Bit # Field Read/Write Default 7 Swap R/W 0 6 LSB First R/W 0 R/W 0 5 Comm Mode R/W 0 4 3 CPOL R/W 0 2 CPHA R/W 0 R/W 0 1 SCLK Select R/W 0 0
Bit 7: Swap 0 = Swap function disabled 1 = The SPI block swaps its use of SMOSI and SMISO. Among other things, this can be useful in implementing single wire SPIlike communications Bit 6: LSB First 0 = The SPI transmits and receives the MSB (Most Significant Bit) first 1 = The SPI transmits and receives the LSB (Least Significant Bit) first. Bit [5:4]: Comm Mode [1:0] 0 0: All SPI communication disabled 0 1: SPI master mode 1 0: SPI slave mode 1 1: Reserved Bit 3: CPOL This bit controls the SPI clock (SCLK) idle polarity 0 = SCLK idles low 1 = SCLK idles high Bit 2: CPHA The Clock Phase bit controls the phase of the clock on which data is sampled. Table 15-3 below shows the timing for the various combinations of LSB First, CPOL, and CPHA Bit [1:0]: SCLK Select This field selects the speed of the master SCLK. When in master mode, SCLK is generated by dividing the base CPUCLK Important Note for Comm Modes 01b or 10b (SPI Master or SPI Slave): When configured for SPI, (SPI Use = 1--Table 14-14), the input/output direction of pins P1.3, P1.5, and P1.6 is set automatically by the SPI logic. However, pin P1.4's input/output direction is NOT automatically set; it must be explicitly set by firmware. For SPI Master mode, pin P1.4 must be configured as an output; for SPI Slave mode, pin P1.4 must be configured as an input.
Document 38-08035 Rev. *I
Page 37 of 74
[+] Feedback
CY7C63310 CY7C638xx
15.3 SPI Interface Pins
The SPI interface uses the P1.3-P1.6 pins. These pins are configured using the P1.3 and P1.4-P1.6 Configuration. Table 15-3. SPI Mode Timing vs. LSB First, CPOL and CPHA
LSB First CPHA CPOL 0 0 0 Diagram
SCLK SSEL D AT A
0 0 1
SC LK SSEL DAT A
X
MSB B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LSB
X
MSB
B it 7
B it 6
B it 5
B it 4
B it 3
B it 2
LSB
X
X
0
1
0
SC LK SSEL DAT A
0 1 1
X
MSB B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LS B
X
SC L K SSEL D AT A
1 0 0
X
MS B B it 7 B it 6 B it 5 B it 4 B it 3 B it 2 LS B
X
SCLK SSEL DAT A
1 0 1
X
LSB B it 2 B it 3 B it 4 B it 5 B it 6 B it 7 MS B
X
SCLK SSEL DAT A
1 1 0
X
LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB
X
SCLK SSEL DAT A
1 1 1
X
LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB
X
SC LK SSEL DAT A
X
LSB Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 MSB
X
Document 38-08035 Rev. *I
Page 38 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 15-4. SPI SCLK Frequency
SCLK Select 00 01 10 11 CPUCLK Divisor 6 12 48 96 SCLK Frequency when CPUCLK = 12 MHz 2 MHz 1 MHz 250 KHz 125 KHz 24 MHz 4 MHz 2 MHz 500 KHz 250 KHz
16.0
Timer Registers
All timer functions of the enCoRe II are provided by a single timer block. The timer block is asynchronous from the CPU clock.
16.1
16.1.1
Registers
Free Running Counter
The 16 bit free-running counter is clocked by the Timer Capture Clock (TCAPCLK). It can be read in software for use as a generalpurpose time base. When the low-order byte is read, the high-order byte is registered. Reading the high-order byte reads this register allowing the CPU to read the 16-bit value atomically (loads all bits at one time). The free-running timer generates an interrupt at 1024-s rate when clocked by a 4MHz source. It can also generate an interrupt when the free-running counter overflow occurs--every 16.384 ms(with a 4MHz source). This allows extending the length of the timer in software.. Figure 16-1. 16-bit Free Running Counter Block Diagram
O verflow Interrupt/W rap Interrupt
Tim er C apture C lock
16-bit Free R unning C ounter
1024s T im er Interrupt
Table 16-1. Free-running Timer Low-order Byte (FRTMRL) [0x20] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Free-running Timer [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Free-running Timer [7:0] This register holds the low-order byte of the 16-bit free-running timer. Reading this register causes the high-order byte to be moved into a holding register allowing an automatic read of all 16 bits simultaneously. For reads, the actual read occurs in the cycle when the low order is read. For writes, the actual time the write occurs is the cycle when the high order is written. When reading the Free Running Timer, the low-order byte must be read first and the high-order second. When writing, the loworder byte must be written first then the high-order byte
Document 38-08035 Rev. *I
Page 39 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 16-2. Free-running Timer High-order Byte (FRTMRH) [0x21] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Free-running Timer [15:8] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Free-running Timer [15:8] When reading the Free-running Timer, the low-order byte must be read first and the high-order second. When writing, the loworder byte must be written first then the high-order byte Table 16-3. Timer Capture 0 Rising (TCAP0R) [0x22] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Capture 0 Rising [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Capture 0 Rising [7:0] This register holds the value of the Free-running Timer when the last rising edge occurred on the TCAP0 input. When Capture 0 is in 8-bit mode, the bits that are stored here are selected by the Prescale [2:0] bits in the Timer Configuration register. When Capture 0 is in 16-bit mode this register holds the lower order 8 bits of the 16-bit timer
Table 16-4. Timer Capture 1 Rising (TCAP1R) [0x23] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Capture 1 Rising [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Capture 1 Rising [7:0] This register holds the value of the Free-running Timer when the last rising edge occurred on the TCAP1 input. The bits that are stored here are selected by the Prescale [2:0] bits in the Timer Configuration register. When Capture 0 is in 16-bit mode this register holds the high-order 8 bits of the 16-bit timer from the last Capture 0 rising edge. When Capture 0 is in 16-bit mode this register will be loaded with high-order 8 bits of the 16-bit timer on TCAP0 rising edge Table 16-5. Timer Capture 0 Falling (TCAP0F) [0x24] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Capture 0 Falling [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Capture 0 Falling [7:0] This register holds the value of the Free-running Timer when the last falling edge occurred on the TCAP0 input. When Capture 0 is in 8-bit mode, the bits that are stored here are selected by the Prescale [2:0] bits in the Timer Configuration register. When Capture 0 is in 16-bit mode this register holds the lower-order 8 bits of the 16-bit timer Table 16-6. Timer Capture 1 Falling (TCAP1F) [0x25] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Capture 1 Falling [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Capture 1Falling [7:0] This register holds the value of the Free-running Timer when the last falling edge occurred on the TCAP1 input. The bits that are stored here are selected by the Prescale [2:0] bits in the Timer Configuration register. When capture 0 is in 16-bit mode this register holds the high-order 8 bits of the 16-bit timer from the last Capture 0 falling edge. When Capture 0 is in 16-bit mode this register will be loaded with high-order 8 bits of the 16-bit timer on TCAP0 falling edge
Document 38-08035 Rev. *I
Page 40 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 16-7. Programmable Interval Timer Low (PITMRL) [0x26] [R]
Bit # Field Read/Write Default R 0 R 0 R 0 7 6 5 4 3 2 1 0
Prog Interval Timer [7:0] R 0 R 0 R 0 R 0 R 0
Bit [7:0]: Prog Interval Timer [7:0] This register holds the low-order byte of the 12-bit programmable interval timer. Reading this register causes the high-order byte to be moved into a holding register allowing an automatic read of all 12 bits simultaneously Table 16-8. Programmable Interval Timer High (PITMRH) [0x27] [R]
Bit # Field Read/Write Default - 0 - 0 7 6 Reserved - 0 - 0 R 0 5 4 3 2 1 0
Prog Interval Timer [11:8] R 0 R 0 R 0
Bit [7:4]: Reserved Bit [3:0]: Prog Internal Timer [11:8] This register holds the high-order nibble of the 12-bit programmable interval timer. Reading this register returns the high-order nibble of the 12-bit timer at the instant that the low-order byte was last read Table 16-9. Programmable Interval Reload Low (PIRL) [0x28] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Prog Interval [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
Bit [7:0]: Prog Interval [7:0] This register holds the lower 8 bits of the timer. While writing into the 12-bit reload register, write lower byte first then the higher nibble Table 16-10. Programmable Interval Reload High (PIRH) [0x29] [R/W]
Bit # Field Read/Write Default - 0 - 0 7 6 Reserved - 0 - 0 R/W 0 5 4 3 2 1 0
Prog Interval[11:8] R/W 0 R/W 0 R/W 0
Bit [7:4]: Reserved Bit [3:0]: Prog Interval [11:8] This register holds the higher 4 bits of the timer. While writing into the 12-bit reload register, write lower byte first then the higher nibble 16.1.2 Timer Capture configured in this way, the capture 1 registers hold the high order byte of the 16-bit timer capture value. Each of the four capture registers can be programmed to generatean interrupt when it is loaded.
enCoRe II has two 8-bit captures. Each capture has separate registers for the rising and falling time. The two eight bit captures can be configured as a single 16-bit capture. When
Document 38-08035 Rev. *I
Page 41 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 16-2. Programmable Interval Timer Block Diagram
S y s te m C lo c k
C o n fig u r a tio n S ta tu s a n d C o n tro l
1 2 - b it r e lo a d v a lu e
C lo c k T im e r
1 2 - b it d o w n c o u n te r
1 2 - b it r e lo a d c o u n te r
In te rru p t C o n tr o lle r
Table 16-11. Timer Configuration (TMRCR) [0x2A] [R/W]
Bit # Field Read/Write Default 7 First Edge Hold R/W 0 R/W 0 6 5 8-bit Capture Prescale [2:0] R/W 0 R/W 0 4 3 Cap0 16bit Enable R/W 0 - 0 2 1 Reserved - 0 - 0 0
Bit 7: First Edge Hold The First Edge Hold function applies to all four capture timers. 0 = The time of the most recent edge is held in the Capture Timer Data Register. If multiple edges have occurred since reading the capture timer, the time for the most recent one will be read 1 = The time of the first occurrence of an edge is held in the Capture Timer Data Register until the data is read. Subsequent edges are ignored until the Capture Timer Data Register is read. Bit [6:4]: 8-bit Capture Prescale [2:0] This field controls which 8 bits of the 16 Free Running Timer are captured when in bit mode 0 0 0 = capture timer[7:0] 0 0 1 = capture timer[8:1] 0 1 0 = capture timer[9:2] 0 1 1 = capture timer[10:3] 1 0 0 = capture timer[11:4] 1 0 1 = capture timer[12:5] 1 1 0 = capture timer[13:6] 1 1 1 = capture timer[14:7] Bit 3: Cap0 16-bit Enable 0 = Capture 0 16-bit mode is disabled 1 = Capture 0 16-bit mode is enabled. Capture 1 is disabled and the Capture 1 rising and falling registers are used as an extension to the Capture 0 registers--extending them to 16 bits Bit [2:0]: Reserved
Document 38-08035 Rev. *I
Page 42 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 16-12. Capture Interrupt Enable (TCAPINTE) [0x2B] [R/W]
Bit # Field Read/Write Default - 0 - 0 7 6 Reserved - 0 - 0 5 4 3 Cap1 Fall Enable R/W 0 2 Cap1 Rise Enable R/W 0 1 Cap0 Fall Enable R/W 0 0 Cap0 Rise Enable R/W 0
Bit [7:4]: Reserved Bit 3: Cap1 Fall Enable 0 = Disable the capture 1 falling edge interrupt 1 = Enable the capture 1 falling edge interrupt Bit 2: Cap1 Rise Enable 0 = Disable the capture 1 rising edge interrupt 1 = Enable the capture 1 rising edge interrupt Bit 1: Cap0 Fall Enable 0 = Disable the capture 0 falling edge interrupt 1 = Enable the capture 0 falling edge interrupt Bit 0: Cap0 Rise Enable 0 = Disable the capture 0 rising edge interrupt 1 = Enable the capture 0 rising edge interrupt
Table 16-13. Capture Interrupt Status (TCAPINTS) [0x2C] [R/W]
Bit # Field Read/Write Default - 0 - 0 7 6 Reserved - 0 - 0 5 4 3 Cap1 Fall Active R/W 0 2 Cap1 Rise Active R/W 0 1 Cap0 Fall Active R/W 0 0 Cap0 Rise Active R/W 0
Bit [7:4]: Reserved Bit 3: Cap1 Fall Active 0 = No event 1 = A falling edge has occurred on Cap1 Bit 2: Cap1 Rise Active 0 = No event 1 = A rising edge has occurred on Cap1 Bit 1: Cap0 Fall Active 0 = No event 1 = A falling edge has occurred on Cap0 Bit 0: Cap0 Rise Active 0 = No event 1 = A rising edge has occurred on Cap0 Note: The interrupt status bits must be cleared by firmware to enable subsequent interrupts. This is achieved by writing a `1' to the corresponding Interrupt status bit.
Document 38-08035 Rev. *I
Page 43 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 16-3. Timer Functional Timing Diagram
clk_captimer 16-bit free running counter clk_sys capture0 cap0_rise cap0_fall capture1 cap1_rise cap1_fall cap0_rise_reg cap0_fall_reg cap1_rise_reg cap1_fall_reg Timing diagrams when cap0 is in 8 bit mode cap1_rise_reg cap1_fall_reg Timing diagrams when cap0 is in 16 bit mode
Document 38-08035 Rev. *I
Page 44 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 16-4. 16-bit Free Running Counter Loading Timing Diagram
clk_sys write
valid addr write data FRT reload ready Clk Timer 12b Prog Timer 12b reload interrupt 12-bit programmable timer load timing Capture timer clk 16b free running counter load 16b free running counter
00A0 00A1 00A2 00A3 00A4 00A5 00A6 00A7 00A8 00A9 00AB 00AC 00AD 00AE 00AF 00B0 00B1 00B2 ACBE ACBF ACC0
16-bit free running counter loading timing
Figure 16-5. Memory Mapped Registers Read/Write Timing Diagram
clk_sys rd_wrn
Valid Addr rdata wdata Memory mapped registers Read/Write timing diagram
Document 38-08035 Rev. *I
Page 45 of 74
[+] Feedback
CY7C63310 CY7C638xx
17.0 Interrupt Controller
Table 17-1. Interrupt Numbers, Priorities, Vectors (continInterrupt Priority 17 18 19 20 21 22 23 Table 17-1. Interrupt Numbers, Priorities, Vectors Interrupt Priority 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Interrupt Address 0000h 0004h 0008h 000Ch 0010h 0014h 0018h 001Ch 0020h 0024h 0028h 002Ch 0030h 0034h 0038h 003Ch 0040h Reset POR/LVD INT0 SPI Transmitter Empty SPI Receiver Full GPIO Port 0 GPIO Port 1 INT1 EP0 EP1 EP2 USB Reset USB Active 1 mS Interval timer Programmable Interval Timer Timer Capture 0 Timer Capture 1 Figure 17-1. Interrupt Controller Block Diagram Name 24 25 Interrupt Address 0044h 0048h 004Ch 0050h 0054h 0058h 005Ch 0060h 0064h INT2 PS2 Data Low GPIO Port 2 GPIO Port 3 Reserved Reserved Reserved Sleep Timer Name 16-bit Free Running Timer Wrap
The interrupt controller and its associated registers allow the user's code to respond to an interrupt from almost every functional block in the enCoRe II devices. The registers associated with the interrupt controller allow interrupts to be disabled either globally or individually. The registers also provide a mechanism by which a user may clear all pending and posted interrupts, or clear individual posted or pending interrupts. The following table lists all interrupts and the priorities that are available in the enCoRe II devices.
17.1
Architectural Description
An interrupt is posted when its interrupt conditions occur. This results in the flip-flop in Figure 17-1 clocking in a `1'. The interrupt will remain posted until the interrupt is taken or until it is cleared by writing to the appropriate INT_CLRx register. A posted interrupt is not pending unless it is enabled by setting its interrupt mask bit (in the appropriate INT_MSKx register). All pending interrupts are processed by the Priority Encoder to determine the highest priority interrupt which will be taken by the M8C if the Global Interrupt Enable bit is set in the CPU_F register. Disabling an interrupt by clearing its interrupt mask bit (in the INT_MSKx register) does not clear a posted interrupt, nor does it prevent an interrupt from being posted. It simply prevents a posted interrupt from becoming pending. Nested interrupts can be accomplished by re-enabling interrupts inside an interrupt service routine. To do this, set the IE bit in the Flag Register. A block diagram of the enCoRe II Interrupt Controller is shown in Figure 17-1.
Interrupt Taken or INT_CLRx Write Posted Interrupt Pending Interrupt
Priority Encoder
Interrupt Vector
Interrupt Request M8C Core
R 1 Interrupt Source (Timer, GPIO, etc.) INT_MSKx Mask Bit Setting D Q
... ...
CPU_F[0] GIE
Document 38-08035 Rev. *I
Page 46 of 74
[+] Feedback
CY7C63310 CY7C638xx
17.2 Interrupt Processing
The sequence of events that occur during interrupt processing is as follows: 1. An interrupt becomes active, either because: a. The interrupt condition occurs (e.g., a timer expires) b. A previously posted interrupt is enabled through an update of an interrupt mask register c. An interrupt is pending and GIE is set from 0 to 1 in the CPU Flag register. 2. The current executing instruction finishes. 3. The internal interrupt is dispatched, taking 13 cycles. During this time, the following actions occur: he MSB and LSB of Program Counter and Flag registers (CPU_PC and CPU_F) are stored onto the program stack by an automatic CALL instruction (13 cycles) generated during the interrupt acknowledge process. a. The PCH, PCL, and Flag register (CPU_F) are stored onto the program stack (in that order) by an automatic CALL instruction (13 cycles) generated during the interrupt acknowledge process b. The CPU_F register is then cleared. Since this clears the GIE bit to 0, additional interrupts are temporarily disabled c. The PCH (PC[15:8]) is cleared to zero d. The interrupt vector is read from the interrupt controller and its value placed into PCL (PC[7:0]). This sets the program counter to point to the appropriate address in the interrupt table (e.g., 0004h for the POR/LVD interrupt) 4. Program execution vectors to the interrupt table. Typically, a LJMP instruction in the interrupt table sends execution to the user's Interrupt Service Routine (ISR) for this interrupt 5. The ISR executes. Note that interrupts are disabled since GIE = 0. In the ISR, interrupts can be re-enabled if desired by setting GIE = 1 (care must be taken to avoid stack overflow). 6. The ISR ends with a RETI instruction which restores the Program Counter and Flag registers (CPU_PC and CPU_F). The restored Flag register re-enables interrupts, since GIE = 1 again. Table 17-2. Interrupt Clear 0 (INT_CLR0) [0xDA] [R/W]
Bit # Field Read/Write Default 7 GPIO Port 1 R/W 0 6 Sleep Timer R/W 0 5 INT1 R/W 0 4 GPIO Port 0 R/W 0 3 SPI Receive R/W 0 2 SPI Transmit R/W 0 1 INT0 R/W 0 0 POR/LVD R/W 0
7. Execution resumes at the next instruction, after the one that occurred before the interrupt. However, if there are more pending interrupts, the subsequent interrupts will be processed before the next normal program instruction.
17.3
Interrupt Trigger Conditions
Trigger conditions for most interrupts in Table 17-1.have been explained in the relevant sections. However, conditions under which the USB Active (interrupt address 0030h) and PS2 Data Low (interrupt address 004Ch) interrupts are triggered are explained below. 1. USB Active Interrupt: Triggered when the D+/- lines are in a non-idle state i.e., K-state or SE0 state 2. PS2 Data Low Interrupt: Triggered when SDATA becomes low when the SDATA pad is in the input mode for at least 6-7 32 KHz cycles.
17.4
Interrupt Latency
The time between the assertion of an enabled interrupt and the start of its ISR can be calculated from the following equation. Latency = Time for current instruction to finish + Time for internal interrupt routine to execute + Time for LJMP instruction in interrupt table to execute. For example, if the 5-cycle JMP instruction is executing when an interrupt becomes active, the total number of CPU clock cycles before the ISR begins would be as follows: (1 to 5 cycles for JMP to finish) + (13 cycles for interrupt routine) + (7 cycles for LJMP) = 21 to 25 cycles. In the example above, at 24 MHz, 25 clock cycles take 1.042 s.
17.5
Interrupt Registers
The Interrupt Clear Registers (INT_CLRx) are used to enable the individual interrupt sources' ability to clear posted interrupts. When an INT_CLRx register is read, any bits that are set indicates an interrupt has been posted for that hardware resource. Therefore, reading these registers gives the user the ability to determine all posted interrupts.
When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a `1' to the bits AND to the ENSWINT (Bit 7 of the INT_MSK3 Register) will post the corresponding hardware interrupt Table 17-3. Interrupt Clear 1 (INT_CLR1) [0xDB] [R/W]
Bit # Field Read/Write 7 TCAP0 R/W 6 Prog Interval Timer R/W 5 1-ms Timer R/W 4 USB Active R/W 3 USB Reset R/W 2 USB EP2 R/W 1 USB EP1 R/W 0 USB EP0 R/W
Document 38-08035 Rev. *I
Page 47 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 17-3. Interrupt Clear 1 (INT_CLR1) [0xDB] [R/W] (continued)
Default 0 0 0 0 0 0 0 0
When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a 57`1' to the bits AND to the ENSWINT (Bit 7 of the INT_MSK3 Register) will post the corresponding hardware interrupt Table 17-4. Interrupt Clear 2 (INT_CLR2) [0xDC] [R/W]
Bit # Field Read/Write Default 7 Reserved R/W 0 6 Reserved R/W 0 5 GPIO Port 3 R/W 0 4 GPIO Port 2 R/W 0 3 PS/2 Data Low R/W 0 2 INT2 R/W 0 1 16-bit Counter Wrap R/W 0 0 TCAP1 R/W 0
When reading this register, 0 = There's no posted interrupt for the corresponding hardware 1 = Posted interrupt for the corresponding hardware present Writing a `0' to the bits will clear the posted interrupts for the corresponding hardware. Writing a `1' to the bits AND to the ENSWINT (Bit 7 of the INT_MSK3 Register) will post the corresponding hardware interrupt 17.5.1 Interrupt Mask Registers The Enable Software Interrupt (ENSWINT) bit in INT_MSK3[7] determines the way an individual bit value written to an INT_CLRx register is interpreted. When is cleared, writing 1's to an INT_CLRx register has no effect. However, writing 0's to an INT_CLRx register, when ENSWINT is cleared, will cause the corresponding interrupt to clear. If the ENSWINT bit is set, any 0s written to the INT_CLRx registers are ignored. However, 1s written to an INT_CLRx register, while ENSWINT is set, will cause an interrupt to post for the corresponding interrupt. Software interrupts can aid in debugging interrupt service routines by eliminating the need to create system level interactions that are sometimes necessary to create a hardwareonly interrupt.
The Interrupt Mask Registers (INT_MSKx) are used to enable the individual interrupt sources' ability to create pending interrupts. There are four Interrupt Mask Registers (INT_MSK0, INT_MSK1, INT_MSK2, and INT_MSK3) which may be referred to in general as INT_MSKx. If cleared, each bit in an INT_MSKx register prevents a posted interrupt from becoming a pending interrupt (input to the priority encoder). However, an interrupt can still post even if its mask bit is zero. All INT_MSKx bits are independent of all other INT_MSKx bits. If an INT_MSKx bit is set, the interrupt source associated with that mask bit may generate an interrupt that will become a pending interrupt. Table 17-5. Interrupt Mask 3 (INT_MSK3) [0xDE] [R/W]
Bit # Field Read/Write Default 7 ENSWINT R/W 0 - 0 - 0 - 0 6 5 4
3 Reserved - 0
2
1
0
- 0
- 0
- 0
Bit 7: Enable Software Interrupt (ENSWINT) 0= Disable. Writing 0s to an INT_CLRx register, when ENSWINT is cleared, will cause the corresponding interrupt to clear 1= Enable. Writing 1s to an INT_CLRx register, when ENSWINT is set, will cause the corresponding interrupt to post. Bit [6:0]: Reserved Table 17-6. Interrupt Mask 2 (INT_MSK2) [0xDF] [R/W]
Bit # Field Read/Write Default 7 Reserved - 0 6 Reserved R/W 0 5 GPIO Port 3 Int Enable R/W 0 4 GPIO Port 2 Int Enable R/W 0 3 PS/2 Data Low Int Enable R/W 0 2 INT2 Int Enable R/W 0 1 16-bit Counter Wrap Int Enable R/W 0 0 TCAP1 Int Enable R/W 0
Document 38-08035 Rev. *I
Page 48 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 17-6. Interrupt Mask 2 (INT_MSK2) [0xDF] [R/W] (continued) Bit 7: Reserved Bit 6: GPIO Port 4 Interrupt Enable 0 = Mask GPIO Port 4 interrupt 1 = Unmask GPIO Port 4 interrupt Bit 5: GPIO Port 3 Interrupt Enable 0 = Mask GPIO Port 3 interrupt 1 = Unmask GPIO Port 3 interrupt Bit 4: GPIO Port 2 Interrupt Enable 0 = Mask GPIO Port 2 interrupt 1 = Unmask GPIO Port 2 interrupt Bit 3: PS/2 Data Low Interrupt Enable 0 = Mask PS/2 Data Low interrupt 1 = Unmask PS/2 Data Low interrupt Bit 2: INT2 Interrupt Enable 0 = Mask INT2 interrupt 1 = Unmask INT2 interrupt Bit 1: 16-bit Counter Wrap Interrupt Enable 0 = Mask 16-bit Counter Wrap interrupt 1 = Unmask 16-bit Counter Wrap interrupt Bit 0: TCAP1 Interrupt Enable 0 = Mask TCAP1 interrupt 1 = Unmask TCAP1 interrupt
Table 17-7. Interrupt Mask 1 (INT_MSK1) [0xE1] [R/W]
Bit # Field 7 TCAP0 Int Enable R/W 0 6 Prog Interval Timer Int Enable R/W 0 5 1-ms Timer Int Enable R/W 0 4 USB Active Int Enable R/W 0 3 USB Reset Int Enable R/W 0 2 USB EP2 Int Enable R/W 0 1 USB EP1 Int Enable R/W 0 0 USB EP0 Int Enable R/W 0
Read/Write Default
Bit 7: TCAP0 Interrupt Enable 0 = Mask TCAP0 interrupt 1 = Unmask TCAP0 interrupt Bit 6: Prog Interval Timer Interrupt Enable 0 = Mask Prog Interval Timer interrupt 1 = Unmask Prog Interval Timer interrupt Bit 5: 1-ms Timer Interrupt Enable 0 = Mask 1-ms interrupt 1 = Unmask 1-ms interrupt Bit 4: USB Active Interrupt Enable 0 = Mask USB Active interrupt 1 = Unmask USB Active interrupt Bit 3: USB Reset Interrupt Enable 0 = Mask USB Reset interrupt 1 = Unmask USB Reset interrupt Bit 2: USB EP2 Interrupt Enable 0 = Mask EP2 interrupt 1 = Unmask EP2 interrupt Bit 1: USB EP1 Interrupt Enable 0 = Mask EP1 interrupt 1 = Unmask EP1 interrupt Bit 0: USB EP0 Interrupt Enable 0 = Mask EP0 interrupt 1 = Unmask EP0 interrupt
Table 17-8. Interrupt Mask 0 (INT_MSK0) [0xE0] [R/W]
Bit # Field Read/Write Default 7 GPIO Port 1 Int Enable R/W 0 6 Sleep Timer Int Enable R/W 0 5 INT1 Int Enable R/W 0 4 GPIO Port 0 Int Enable R/W 0 3 SPI Receive Int Enable R/W 0 2 SPI Transmit Int Enable R/W 0 1 INT0 Int Enable R/W 0 0 POR/LVD Int Enable R/W 0
Document 38-08035 Rev. *I
Page 49 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 17-8. Interrupt Mask 0 (INT_MSK0) [0xE0] [R/W] Bit 7: GPIO Port 1 Interrupt Enable 0 = Mask GPIO Port 1 interrupt 1 = Unmask GPIO Port 1 interrupt Bit 6: Sleep Timer Interrupt Enable 0 = Mask Sleep Timer interrupt 1 = Unmask Sleep Timer interrupt Bit 5: INT1 Interrupt Enable 0 = Mask INT1 interrupt 1 = Unmask INT1 interrupt Bit 4: GPIO Port 0 Interrupt Enable 0 = Mask GPIO Port 0 interrupt 1 = Unmask GPIO Port 0 interrupt Bit 3: SPI Receive Interrupt Enable 0 = Mask SPI Receive interrupt 1 = Unmask SPI Receive interrupt Bit 2: SPI Transmit Interrupt Enable 0 = Mask SPI Transmit interrupt 1 = Unmask SPI Transmit interrupt Bit 1: INT0 Interrupt Enable 0 = Mask INT0 interrupt 1 = Unmask INT0 interrupt Bit 0: POR/LVD Interrupt Enable 0 = Mask POR/LVD interrupt 1 = Unmask POR/LVD interrupt
Table 17-9. Interrupt Vector Clear Register (INT_VC) [0xE2] [R/W]
Bit # Field Read/Write Default R/W 0 R/W 0 R/W 0 7 6 5 4 3 2 1 0
Pending Interrupt [7:0] R/W 0 R/W 0 R/W 0 R/W 0 R/W 0
The Interrupt Vector Clear Register (INT_VC) holds the interrupt vector for the highest priority pending interrupt when read, and when written will clear all pending interrupts Bit [7:0]: Pending Interrupt [7:0] 8-bit data value holds the interrupt vector for the highest priority pending interrupt. Writing to this register will clear all pending interrupts.
18.0
USB/PS2 Transceiver
Although the USB transceiver has features to assist in interfacing to PS/2 these features are not controlled using these registers. These registers only control the USB interfacing features. PS/2 interfacing options are controlled by the D+/D- GPIO Configuration register (See Table 14-2).
Document 38-08035 Rev. *I
Page 50 of 74
[+] Feedback
CY7C63310 CY7C638xx
18.1 USB Transceiver Configuration
Table 18-1. USB Transceiver Configure Register (USBXCR) [0x74] [R/W]
Bit # Field Read/Write Default 7 USB Pull-up Enable R/W 0 - 0 - 0 - 0 6 5 4 Reserved - 0 - 0 - 0 3 2 1 0 USB Force State R/W 0
Bit 7: USB Pull-up Enable 0 = Disable the pull-up resistor on D- 1 = Enable the pull-up resistor on D-. This pull up is to VCC IF VREG is not enabled or to the internally generated 3.3V when VREG is enabled Bit [6:1]: Reserved Bit 0: USB Force State This bit allows the state of the USB I/O pins D- and D+ to be forced to a state while USB is enabled 0 = Disable USB Force State 1 = Enable USB Force State. Allows the D- and D+ pins to be controlled by P1.1 and P1.0 respectively when the USBIO is in USB mode. Refer to Table 14-2 for more information Note: The USB transceiver has a dedicated 3.3V regulator for USB signalling purposes and to provide for the 1.5K D-pull-up. Unlike the other 3.3V regulator, this regulator cannot be controlled/accessed by firmware. When the device is suspended, this regulator is disabled along with the bandgap (which provides the reference voltage to the regulator) and the D-line is pulled up to 5V through an alternate 6.5K resistor. During wake up following a suspend, the band gap and the regulator are switched on in any order. Under an extremely rare case when the device wakes up following a bus reset condition and the voltage regulator and the band gap turn on in that particular order, there is possibility of a glitch/low pulse occurring on the D- line. The host can misinterpret this as a deattach condition. This condition, although rare, can be avoided by keeping the bandgap circuitry enabled during sleep. This is achieved by setting the `No Buzz' bit, bit[5] in the OSC_CR0 register. This is an issue only if the device is put to sleep during a bus reset condition.
Document 38-08035 Rev. *I
Page 51 of 74
[+] Feedback
CY7C63310 CY7C638xx
19.0
19.1
USB Regulator Output
VREG Control
Table 19-1. VREG Control Register (VREGCR) [0x73] [R/W]
Bit # Field Read/Write Default - 0 - 0 - 0 7 6 5 Reserved - 0 - 0 - 0 4 3 2 1 Keep Alive R/W 0 0 VREG Enable R/W 0
Bit [7:2]: Reserved Bit 1: Keep Alive Keep Alive, when set, allows the voltage regulator to source up to 20 A of current when the voltage regulator is disabled, P12CR[0],P12CR[7] must be cleared. 0 = Disabled 1 = Enabled Bit 0: VREG Enable This bit turns on the 3.3V voltage regulator. The voltage regulator only functions within specifications when VCC is above 4.35V. This block must not be enabled when VCC is below 4.35V--although no damage or irregularities will occur if it is enabled below 4.35V 0 = Disable the 3.3V voltage regulator output on the VREG/P1.2 pin 1 = Enable the 3.3V voltage regulator output on the VREG/P1.2 pin. GPIO functionality of P1.2 is disabled Note: Use of the alternate drive on pins P1.3-P1.6 requires that the VREG Enable bit be set to enable the regulator and provide the alternate voltage
20.0
USB Serial Interface Engine (SIE)
The SIE allows the microcontroller to communicate with the USB host at low-speed data rates (1.5 Mbps). The SIE simplifies the interface between the microcontroller and USB by incorporating hardware that handles the following USB bus activity independently of the microcontroller: * Translate the encoded received data and format the data to be transmitted on the bus. * CRC checking and generation. Flag the microcontroller if errors exist during transmission. * Address checking. Ignore the transactions not addressed to the device.
* Send appropriate ACK/NAK/STALL handshakes. * Token type identification (SETUP, IN, or OUT). Set the appropriate token bit once a valid token is received. * Place valid received data in the appropriate endpoint FIFOs. * Send and update the data toggle bit (Data1/0). * Bit stuffing/unstuffing. Firmware is required to handle the rest of the USB interface with the following tasks: * Coordinate enumeration by decoding USB device requests. * Fill and empty the FIFOs. * Suspend/Resume coordination. * Verify and select Data toggle values.
Document 38-08035 Rev. *I
Page 52 of 74
[+] Feedback
CY7C63310 CY7C638xx
21.0
21.1
USB Device
USB Device Address
Table 21-1. USB Device Address (USBCR) [0x40] [R/W]
Bit # Field Read/Write Default 7 USB Enable R/W 0 R/W 0 R/W 0 R/W 0 6 5 4 3 Device Address[6:0] R/W 0 R/W 0 R/W 0 R/W 0 2 1 0
The content of this register is cleared when a USB Bus Reset condition occurs Bit 7: USB Enable This bit must be enabled by firmware before the serial interface engine (SIE) will respond to USB traffic at the address specified in Device Address [6:0]. When this bit is cleared, the USB transceiver enters power-down state. User's firmware must clear this bit prior to entering sleep mode to save power 0 = Disable USB device address and put the USB transceiver into power-down state 1 = Enable USB device address and put the USB transceiver into normal operating mode Bit [6:0]: Device Address [6:0] These bits must be set by firmware during the USB enumeration process (i.e., SetAddress) to the non-zero address assigned by the USB host
21.2
Endpoint 0, 1, and 2 Count
Table 21-2. Endpoint 0, 1, and 2 Count (EP0CNT-EP2CNT) [0x41, 0x43, 0x45] [R/W]
Bit # Field Read/Write Default 7 Data Toggle R/W 0 6 Data Valid R/W 0 R/W 0 5 Reserved R/W 0 R/W 0 4 3 2 Byte Count[3:0] R/W 0 R/W 0 R/W 0 1 0
Bit 7: Data Toggle This bit selects the DATA packet's toggle state. For IN transactions, firmware must set this bit to the select the transmitted Data Toggle. For OUT or SETUP transactions, the hardware sets this bit to the state of the received Data Toggle bit. 0 = DATA0 1 = DATA1 Bit 6: Data Valid This bit is used for OUT and SETUP tokens only. This bit is cleared to `0' if CRC, bitstuff, or PID errors have occurred. This bit does not update for some endpoint mode settings 0 = Data is invalid. If enabled, the endpoint interrupt will occur even if invalid data is received 1 = Data is valid Bit [5:4]: Reserved Bit [3:0]: Byte Count Bit [3:0] Byte Count Bits indicate the number of data bytes in a transaction: For IN transactions, firmware loads the count with the number of bytes to be transmitted to the host from the endpoint FIFO. Valid values are 0 to 8 inclusive. For OUT or SETUP transactions, the count is updated by hardware to the number of data bytes received, plus 2 for the CRC bytes. Valid values are 2-10 inclusive. For Endpoint 0 Count Register, whenever the count updates from a SETUP or OUT transaction, the count register locks and cannot be written by the CPU. Reading the register unlocks it. This prevents firmware from overwriting a status update on it.
Document 38-08035 Rev. *I
Page 53 of 74
[+] Feedback
CY7C63310 CY7C638xx
21.3 Endpoint 0 Mode
When the SIE writes to these registers they are locked and the processor cannot write to them until after it has read them. Writing to this register clears the upper four bits regardless of the value written. Because both firmware and the SIE are allowed to write to the Endpoint 0 Mode and Count Registers the SIE provides an interlocking mechanism to prevent accidental overwriting of data. Table 21-3. Endpoint 0 Mode (EP0MODE) [0x44] [R/W]
Bit # Field Read/Write Default 7 Setup Received R/C[4] 0 6 IN Received R/C[4] 0 5 OUT Received R/C[4] 0 4 ACK'd Trans R/C[4] 0 R/W 0 R/W 0 3 2 Mode[3:0] R/W 0 R/W 0 1 0
Bit 7: SETUP Received This bit is set by hardware when a valid SETUP packet is received. It is forced HIGH from the start of the data packet phase of the SETUP transactions until the end of the data phase of a control write transfer and cannot be cleared during this interval. While this bit is set to `1', the CPU cannot write to the EP0 FIFO. This prevents firmware from overwriting an incoming SETUP transaction before firmware has a chance to read the SETUP data. This bit is cleared by any non-locked writes to the register. 0 = No SETUP received 1 = SETUP received Bit 6: IN Received This bit when set indicates a valid IN packet has been received. This bit is updated to `1' after the host acknowledges an IN data packet.When clear, it indicates either no IN has been received or that the host didn't acknowledge the IN data by sending ACK handshake. This bit is cleared by any non-locked writes to the register. 0 = No IN received 1 = IN received Bit 5: OUT Received This bit when set indicates a valid OUT packet has been received and ACKed. This bit is updated to `1' after the last received packet in an OUT transaction. When clear, it indicates no OUT received. This bit is cleared by any non-locked writes to the register. 0 = No OUT received 1 = OUT received Bit 4: ACK'd Transaction The ACK'd transaction bit is set whenever the SIE engages in a transaction to the register's endpoint that completes with a ACK packet. This bit is cleared by any non-locked writes to the register 1 = The transaction completes with an ACK 0 = The transaction does not complete with an ACK Bit [3:0]: Mode [3:0] The endpoint modes determine how the SIE responds to USB traffic that the host sends to the endpoint. The mode controls how the USB SIE responds to traffic and how the USB SIE will change the mode of that endpoint as a result of host packets to the endpoint.
Document 38-08035 Rev. *I
Page 54 of 74
[+] Feedback
CY7C63310 CY7C638xx
21.4 Endpoint 1 and 2 Mode
Table 21-4. Endpoint 1 and 2 Mode (EP1MODE - EP2MODE) [0x45, 0x46] [R/W]
Bit # Field Read/Write Default 7 Stall R/W 0 6 Reserved R/W 0 5 NAK Int Enable R/W 0 4 ACK'd Transaction R/C (Note 4) 0 R/W 0 R/W 0 3 2 Mode[3:0] R/W 0 R/W 0 1 0
Bit 7: Stall When this bit is set the SIE will stall an OUT packet if the Mode Bits are set to ACK-OUT, and the SIE will stall an IN packet if the mode bits are set to ACK-IN. This bit must be clear for all other modes Bit 6: Reserved Bit 5: NAK Int Enable This bit when set causes an endpoint interrupt to be generated even when a transfer completes with a NAK. Unlike enCoRe, enCoRe II family members do not generate an endpoint interrupt under these conditions unless this bit is set 0 = Disable interrupt on NAK'd transactions 1 = Enable interrupt on NAK'd transaction Bit 4: ACK'd Transaction The ACK'd transaction bit is set whenever the SIE engages in a transaction to the register's endpoint that completes with an ACK packet. This bit is cleared by any writes to the register 0 = The transaction does not complete with an ACK 1 = The transaction completes with an ACK Bit [3:0]: Mode [3:0] The endpoint modes determine how the SIE responds to USB traffic that the host sends to the endpoint. The mode controls how the USB SIE responds to traffic and how the USB SIE will change the mode of that endpoint as a result of host packets to the endpoint. Note: When the SIE writes to the EP1MODE or the EP2MODE register it blocks firmware writes to the EP2MODE or the EP1MODE registers respectively (if both writes occur in the same clock cycle). This is because the design employs only one common `update' signal for both EP1MODE and EP2MODE registers. Thus, when SIE writes to say EP1MODE register, the update signal is set and this prevents firmware writes to EP2MODE register. SIE writes to the endpoint mode registers have higher priority than firmware writes. This mode register write block situation can put the endpoints in incorrect modes. Firmware must read the EP1/2MODE registers immediately following a firmware write and rewrite if the value read is incorrect.
Table 21-5. Endpoint 0 Data (EP0DATA) [0x50-0x57] [R/W]
Bit # Field Read/Write Default R/W Unknown R/W Unknown R/W Unknown 7 6 5 4 3 2 1 0 Endpoint 0 Data Buffer [7:0] R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown
The Endpoint 0 buffer is comprised of 8 bytes located at address 0x50 to 0x57 Table 21-6. Endpoint 1 Data (EP1DATA) [0x58-0x5F] [R/W]
Bit # Field Read/Write Default R/W Unknown R/W Unknown R/W Unknown 7 6 5 4 3 2 1 0 Endpoint 1 Data Buffer [7:0] R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown
The Endpoint 1buffer is comprised of 8 bytes located at address 0x58 to 0x5F Table 21-7. Endpoint 2 Data (EP2DATA) [0x60-0x67] [R/W]
Bit # Field 7 6 5 4 3 2 1 0 Endpoint 2 Data Buffer [7:0]
Document 38-08035 Rev. *I
Page 55 of 74
[+] Feedback
CY7C63310 CY7C638xx
Table 21-7. Endpoint 2 Data (EP2DATA) [0x60-0x67] [R/W] (continued)
Read/Write Default R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown R/W Unknown
The Endpoint 2 buffer is comprised of 8 bytes located at address 0x60 to 0x67 The three data buffers used to hold data for both IN and OUT transactions. Each data buffer is 8 bytes long. The reset values of the Endpoint Data Registers are unknown. Unlike past enCoRe parts the USB data buffers are only accessible in the I/O space of the processor.
22.0
USB Mode Tables
Mode DISABLE Encoding 0000 0001 0010 0011 0110 1011 1111 SETUP Ignore Accept Accept Accept Accept Accept Accept IN Ignore NAK STALL STALL TX0 byte TX0 byte TX Count OUT Ignore NAK Check STALL STALL ACK Check Comments Ignore all USB traffic to this endpoint. Used by Data and Control endpoints NAK IN and OUT token. Control endpoint only STALL IN and ACK zero byte OUT. Control endpoint only STALL IN and OUT token. Control endpoint only STALL OUT and send zero byte data for IN token. Control endpoint only ACK the OUT token or send zero byte data for IN token. Control endpoint only Respond to IN data or Status OUT. Control endpoint only
NAK IN/OUT STATUS OUT ONLY STALL IN/OUT STATUS IN ONLY ACK OUT - STATUS IN ACK IN - STATUS OUT NAK OUT ACK OUT (STALL = 0)
1000 1001
Ignore Ignore
Ignore Ignore
NAK ACK
Send NAK handshake to OUT token. Data endpoint only This mode is changed by the SIE to mode 1000 on issuance of ACK handshake to an OUT. Data endpoint only STALL the OUT transfer Send NAK handshake for IN token. Data endpoint only This mode is changed by the SIE to mode 1100 after receiving ACK handshake to an IN data. Data endpoint only STALL the IN transfer. Data endpoint only These modes are not supported by SIE. Firmware must not use this mode in Control and Data endpoints
ACK OUT (STALL = 1) NAK IN ACK IN (STALL = 0)
1001 1100 1101
Ignore Ignore Ignore
Ignore NAK TX Count
STALL Ignore Ignore
ACK IN (STALL = 1) Reserved Reserved Reserved Reserved Reserved
1101 0101 0111 1010 0100 1110
Ignore Ignore Ignore Ignore Ignore Ignore
STALL Ignore Ignore Ignore Ignore Ignore
Ignore Ignore Ignore Ignore Ignore Ignore
Mode Column The 'Mode' column contains the mnemonic names given to the modes of the endpoint. The mode of the endpoint is determined by the four-bit binaries in the 'Encoding' column as discussed below. The Status IN and Status OUT represent the status IN or OUT stage of the control transfer. Encoding Column The contents of the 'Encoding' column represent the Mode Bits [3:0] of the Endpoint Mode Registers (Table 21-3 and Table 21-4). The endpoint modes determine how the SIE responds to different tokens that the host sends to the endpoints. For example, if the Mode Bits [3:0] of the Endpoint 0 Mode Register are set to '0001', which is NAK IN/OUT mode,
the SIE will send an ACK handshake in response to SETUP tokens and NAK any IN or OUT tokens. SETUP, IN, and OUT Columns Depending on the mode specified in the 'Encoding' column, the 'SETUP', 'IN', and 'OUT' columns contain the SIE's responses when the endpoint receives SETUP, IN, and OUT tokens, respectively. A 'Check' in the Out column means that upon receiving an OUT token the SIE checks to see whether the OUT is of zero length and has a Data Toggle (Data1/0) of 1. If these conditions are true, the SIE responds with an ACK. If any of the above conditions is not met, the SIE will respond with either a STALL or Ignore.
Document 38-08035 Rev. *I
Page 56 of 74
[+] Feedback
CY7C63310 CY7C638xx
A 'TX Count' entry in the IN column means that the SIE will transmit the number of bytes specified in the Byte Count Bit [3:0] of the Endpoint Count Register (Table 21-2) in response to any IN token.
23.0
SIE Mode 0000 0011 0011 0011 0011 0011 0011 0011 0001 0001 0001 0001 0001 0001 0001 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 0010 0010 0010 0010 0010 0010 0010 0010 0010 1011 1011 1011
Details of Mode for Differing Traffic Conditions
Bus Event Token x SETUP SETUP SETUP IN OUT OUT OUT SETUP SETUP SETUP IN OUT OUT OUT SETUP SETUP SETUP IN IN OUT OUT OUT OUT OUT SETUP SETUP SETUP IN OUT OUT OUT OUT OUT SETUP SETUP SETUP Count x >10 <=10 <=10 x >10 <=10 <=10 >10 <=10 <=10 x >10 <=10 <=10 >10 <=10 <=10 x x >10 <=10 <=10, <>2 2 2 >10 <=10 <=10 x >10 <=10 <=10, <>2 2 2 >10 <=10 <=10 Dval x x invalid valid x x invalid valid x invalid valid x x invalid valid x invalid valid x x x invalid valid valid valid x invalid valid x x invalid valid valid valid x invalid valid D0/1 x x x x x x x x x x x x x x x x x x x x x x x 0 1 x x x x x x x 0 1 x x x ACK 1 1 0001 update 1 update STALL STALL ACK 11 0011 0011 1 1 2 junk junk data Yes Yes Yes Yes ACK STALL 1 1 0001 0011 update 1 update STALL STALL ACK 11 0011 0011 0010 1 1 2 junk junk data Yes Yes Yes Yes Yes ACK TX TX 1 1 0001 Yes 1 1 0001 update 1 update NAK junk junk data Yes ACK NAK 1 1 0001 update 1 update STALL junk junk data Yes ACK STALL 1 1 0001 update 1 update junk junk data Yes SIE EP0 Mode Register I EP0 Count Register EP0 Interrupt Comments
Control Endpoint Response S O A MODE DTOG DVAL COUNT FIFO Ignore All Ignore Ignore ACK SETUP Stall IN Ignore Ignore Stall OUT Ignore Ignore ACK SETUP NAK IN Ignore Ignore NAK OUT Ignore Ignore ACK SETUP Host Not ACK'd Host ACK'd Ignore Ignore Bad Status Bad Status Good Status Ignore Ignore ACK SETUP Stall IN Ignore Ignore Bad Status Bad Status Good Status Ignore Ignore ACK SETUP
DISABLED STALL_IN_OUT
NAK_IN_OUT
ACK_IN_STATUS_OUT
STATUS_OUT
ACK_OUT_STATUS_IN
Document 38-08035 Rev. *I
Page 57 of 74
[+] Feedback
CY7C63310 CY7C638xx
23.0
1011 1011 1011 1011 1011 0110 0110 0110 0110 0110 0110 0110 0110 SIE Mode 1001 1001 1001 1001 1001 1001 1001 1001 1000 1000 1000 1000 SIE Mode 1101 1101 1101 1101 1101 NAK IN 1100 1100 OUT IN x x x x x x NAK Ignore If Enabled NAK IN Token OUT IN IN OUT IN Token IN OUT OUT OUT IN OUT OUT OUT IN OUT OUT OUT
Details of Mode for Differing Traffic Conditions (continued)
IN IN OUT OUT OUT SETUP SETUP SETUP IN IN OUT OUT OUT x x >10 <=10 <=10 >10 <=10 <=10 x x >10 <=10 <=10 x x x invalid valid x invalid valid x x x invalid valid x x x x x x x x x x x x x STALL SIE D0/1 x x valid x x valid x x valid NAK SIE D0/1 x x x x x STALL TX 1 1100 Yes EP0 Mode Register I EP0 Count Register EP0 STALL ACK 1 1000 update 1 update junk junk data Yes 0011 EP0 Mode Register I EP0 Count Register EP0 Yes Interrupt ACK TX 0 TX 0 1 1 0011 Yes 1 1 0001 update 1 update ACK 11 0001 update 1 update TX 0 TX 0 1 1 0011 junk junk data junk junk data Yes Yes Yes Host Not ACK'd Host ACK'd Ignore Ignore Good OUT Ignore Ignore ACK SETUP Host Not ACK'd Host ACK'd Ignore Ignore Stall OUT Comments
STATUS_IN
Data Out Endpoints Bus Event Count x >MAX <=MAX <=MAX x >MAX <=MAX <=MAX x >MAX <=MAX <=MAX Dval x x valid x x valid x x valid Response S O A MODE DTOG DVAL COUNT FIFO Ignore Ignore Ignore ACK OUT Ignore Ignore Ignore Stall OUT Ignore Ignore Ignore If Enabled NAK OUT Interrupt Comments
ACK OUT (STALL Bit = 0)
invalid invalid
ACK OUT (STALL Bit = 1)
invalid invalid
NAK OUT
invalid invalid
Data In Endpoints Bus Event Count x x x x x Dval x x x x x Response S O A MODE DTOG DVAL COUNT FIFO Ignore Host Not ACK'd Host ACK'd Ignore Stall IN
ACK IN (STALL Bit = 0)
ACK IN (STALL Bit = 1)
Document 38-08035 Rev. *I
Page 58 of 74
[+] Feedback
CY7C63310 CY7C638xx
24.0
Addr 00 01 02 03 04 05 06 07-09 0A-0B 0C 0D 0E 0F 10 11-13 14 15 16 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 30
Register Summary
Name P0DATA P1DATA P2DATA P3DATA P4DATA P00CR P01CR P02CR- P04CR P05CR- P06CR P07CR P10CR P11CR P12CR P13CR P14CR- P16CR P17CR P2CR P3CR FRTMRL FRTMRH TCAP0R TCAP1R TCAP0F TCAP1F PITMRL PITMRH PIRL PIRH TMRCR TCAPINTE TCAPINTS CPUCLKCR Reserved First Edge Hold Reserved 8-bit capture Prescale Reserved Reserved USB CLK/2 Disable USB CLK Select TCAPCLK Select Cap0 16bit Enable Cap1 Fall Active Cap1 Fall Active Cap1 Rise Active Cap1 Rise Active Reserved Prog Interval [7:0] Prog Interval [11:8] Reserved Cap0 Fall Active Cap0 Fall Active Cap0 Rise Active Cap0 Rise Active CPU CLK Select ITMRCLK Select CLKOUT Select Gain[4:0] 32-KHz Freq Trim [3:0] Reserved CLK Output Int Enable Int Enable Res Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low Int Act Low TTL Thresh Reserved TTL Thresh Reserved TTL Thresh Reserved TTL Thresh Reserved TTL Thresh Reserved Reserved Reserved TTL Thresh Reserved 3.3V Drive 3.3V Drive High Sink High Sink Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain Open Drain 7 P0.7 P1.7 6 5 4 3 P0.3/INT1 2 P0.2/INT0 1 0 R/W bbbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb ----bbbb Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable PS/2 Pullup Enable Reserved Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Pull-up Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable Output Enable -bbbbbbb bbbbbbbb --bbbbbb bbbbbbbb -bbbbbbb -bb---bb -bb--b-b bbbbbbbb -bbbbbbb bbbbbbbb -bbbbbbb -bbbbbbb -bbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb bbbbbbbb ----bbbb bbbbbbbb ----bbbb bbbbb------bbbb ----bbbb -bb----b Default 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00010000 P0.6/TIO1 P0.5/TIO0 P0.4/INT2 P0.1/CLK- P0.0/CLKI OUT N P1.1/D- P1.0/D+
P1.6/SMI P1.5/SMO P1.4/SCLK P1.3/SSEL P1.2/VREG SO SI Res Res Res Open Drain Open Drain Open Drain Open Drain Open Drain
P2.1-P2.0 P3.1-P3.0
Reserved Reserved TIO Output Reserved Reserved Reserved CLK Output Reserved SPI Use Reserved Reserved Reserved Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable Int Enable
TTL Thresh High Sink TTL Thresh Reserved TTL Thresh Reserved
Free Running Timer [7:0] Free Running Timer [15:8] Capture 0 Rising [7:0] Capture 1 Rising [7:0] Capture 0 Falling [7:0] Capture 1 Falling [7:0] Prog Interval Timer [7:0] Prog Interval Timer [11:8]
Reserved
31 32 34 36
ITMRCLKCR CLKIOCR IOSCTR LPOSCTR
TCAPCLK Divider Reserved foffset[2:0] 32-KHz Low Power
ITMRCLK Divider Reserved
bbbbbbbb ---bbbbb bbbbbbbb b-bbbbbb
10001111 00000000 000ddddd dddddddd
Reserved 32-KHz Bias Trim [1:0]
39
OSCLCKCR
Reserved
Fine Tune Only
USB Osclock Disable
------bb
00000000
Document 38-08035 Rev. *I
Page 59 of 74
[+] Feedback
CY7C63310 CY7C638xx
24.0
Addr 3C 3D 40 41 42 43 44 45 46 50-57 58-5F 60-67 73 74 DA DB
Register Summary (continued)
Name SPIDATA SPICR USBCR EP0CNT EP1CNT EP2CNT EP0MODE EP1MODE EP2MODE EP0DATA EP1DATA EP2DATA VREGCR USBXCR INT_CLR0 INT_CLR1 USB Pullup Enable GPIO Port 1 TCAP0 Sleep Timer Prog Interval Timer INT1 1-ms Timer Swap USB Enable Data Toggle Data Toggle Data Toggle Setup rcv'd Stall Stall Data Valid Data Valid Data Valid IN rcv'd Reserved Reserved Reserved Reserved Reserved OUT rcv'd ACK'd trans NAK Int Enable NAK Int Enable Ack'd trans Ack'd trans Endpoint 0 Data Buffer [7:0] Endpoint 1 Data Buffer [7:0] Endpoint 2 Data Buffer [7:0] Reserved Reserved GPIO Port 0 SPI Receive SPI Transmit USB EP2 INT0 USB EP1 Keep Alive VREG Enable USB Force State POR/LVD USB EP0 LSB First Comm Mode 7 6 5 4 3 SPIData[7:0] CPOL CPHA SCLK Select 2 1 0 R/W bbbbbbbb bbbbbbbb bbbbbbbb Byte Count[3:0] Byte Count[3:0] Byte Count[3:0] Mode[3:0] Mode[3:0] Mode[3:0] bbbbbbbb bbbbbbbb bbbbbbbb ccccbbbb b-bcbbbb b-bcbbbb bbbbbbbb bbbbbbbb bbbbbbbb ------bb b------b bbbbbbbb bbbbbbbb Default 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ???????? ???????? ???????? 00000000 00000000 00000000 00000000
Device Address[6:0]
USB Active USB Reset
DC
INT_CLR2
Reserved Reserved GPIO Port GPIO Port 2 PS/2 Data 3 Low ENSWINT Reserved
INT2
16-bit Counter Wrap
TCAP1
-bbbbbbb
00000000
DE DF
INT_MSK3 INT_MSK2
b------INT2 Int Enable 16-bit Counter Wrap Int Enable USB EP1 Int Enable TCAP1 Int Enable -bbbbbbb
00000000 00000000
Reserved Reserved GPIO Port GPIO Port 2 PS/2 Data 3 Int Enable Low Int Int Enable Enable TCAP0 Int Enable Prog 1-ms USB Active USB Reset Interval Timer Int Enable Int Enable Timer Int Enable Int Enable
E1
INT_MSK1
USB EP2 Int Enable
USB EP0 Int Enable
bbbbbbbb
00000000
E0
INT_MSK0
GPIO Port Sleep INT1 GPIO Port 0 SPI SPI Transmit INT0 1 Timer Int Enable Int Enable Receive Int Enable Int Enable Int Enable Int Enable Int Enable Pending Interrupt [7:0] Reset Watchdog Timer [7:0] Temporary Register T1 [7:0] X[7:0] Program Counter [7:0] Program Counter [15:8] Stack Pointer [7:0] Reserved GIES Reserved WDRS No Buzz XOI PORS Super Sleep Carry Reserved Zero Reserved
POR/LVD Int Enable
bbbbbbbb
00000000
E2 E3 -----FF 1E0 1E3 1EB 1E4
INT_VC RESWDT CPU_A CPU_X CPU_PCL CPU_PCH CPU_SP CPU_F CPU_SCR OSC_CR0 LVDCR ECO_TR VLTCMP
bbbbbbbb wwwwwwww -----------------------------------Global IE Stop ---brwww r-ccb--b --bbbbbb --bb-bbbb bb-----LVD PPOR ------rr
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000010 00010000 00000000 00000000 00000000 00000000
Reserved Reserved Sleep Duty Cycle [1:0]
Sleep Timer [1:0] Reserved Reserved
CPU Speed [2:0] VM[2:0]
PORLEV[1:0]
Reserved
Legend In the R/W column, b = Both Read and Write r = Read Only w = Write Only c = Read/Clear ? = Unknown
d = calibration value. Must not change during normal use.
Document 38-08035 Rev. *I
Page 60 of 74
[+] Feedback
CY7C63310 CY7C638xx
25.0 Absolute Maximum Ratings
Maximum Total Sink Output Current into Port 0 and 1 and Pins............................................................. 70 mA Maximum Total Source Output Current into GPIO Pins30 mA Maximum On-chip Power Dissipation on any GPIO Pin......................................................... 50 mW Power Dissipation .................................................... 300 mW Static Discharge Voltage ............................................. 2200V Latch-up Current ...................................................... 200 mA
Storage Temperature ..................................-65C to +150C Ambient Temperature with Power Applied ..... -0C to +70C Supply Voltage on VCC Relative to VSS.......... -0.5V to +7.0V DC Input Voltage ................................ -0.5V to + VCC + 0.5V DC Voltage Applied to Outputs in High-Z State ...................................... -0.5V to + VCC + 0.5V
26.0
DC Characteristics
Description General Operating Voltage Operating Voltage Operating Voltage Operating Voltage Operating Temp VCC Operating Supply Current VCC Operating Supply Current Standby Current Conditions No USB activity, CPU speed < 12 MHz USB activity, CPU speed < 12 MHz Flash programming No USB activity, CPU speed < 24 MHz Flash Programming VCC = 5.25V, no GPIO loading, 24 MHz VCC = 5.0V, no GPIO loading, 6 MHz Internal and External Oscillators, Bandgap, Flash, CPU Clock, Timer Clock, USB Clock all disabled 2.681 10 10 Min. 4.0 4.35 4.35 4.75 0 Typical Max. 5.5 5.25 5.25 5.5 70 40 Unit V V V V C mA mA A
Parameter VCC1 VCC2 VCC3 VCC4 TFP ICC1 ICC2 ISB1
Low-voltage Detect VLVD Low-voltage detect Trip Voltage (8 programmable trip points) Max Regulator Output Current Keep Alive Current Keep Alive Voltage VREG Output Voltage VREG Output Voltage Capacitive load on Vreg pin Line Regulation Load Regulation Static Output High Static Output Low Differential Input Sensitivity Differential Input Common Mode Range Single Ended Receiver Threshold Transceiver Capacitance Hi-Z State Data Line Leakage 0V < VIN < 3.3V -10 15K 5% Ohm to VSS RUP is enabled 0.2 0.8 0.8 2.5 2 20 10 2.8 4.35V < VCC < 5.5V When regulator is disabled with "keep alive" enable Keep Alive bit set in VREGCR VCC > 4.35V, 0 < temp < 40C, 25 mA < IVREG < 125 mA (3.3V 8%) T = 0 to 70C VCC > 4.35V, 0 < temp < 40C, 1 mA < IVREG < 25 mA (3.3V 4%) T = 0 to 40C 2.35 3.0 4.872 V
3.3V Regulator IVREG IKA VKA VREG1 VREG2 CLOAD LNREG LDREG VON VOFF VDI VCM VSE CIN IIO 125 20 3.8 3.6 mA A V V
3.15
3.45
V F %/V %/mA V V V V V pF A
1
2 1 0.04 3.6 0.3
USB Interface
Document 38-08035 Rev. *I
Page 61 of 74
[+] Feedback
CY7C63310 CY7C638xx
26.0 DC Characteristics (continued)
Description Parameter PS/2 Interface VOLP RPS2 RUP VICR VICF VHC VILTTL VIHTTL VOL1 VOL2 VOL3 VOH CLOAD Static Output Low Internal PS/2 Pull up Resistance Pull up Resistance Input Threshold Voltage Low, CMOS Low to High edge mode Input Threshold Voltage Low, CMOS High to Low edge mode Input Hysteresis Voltage, CMOS Mode High to low edge Input Low Voltage, TTL Mode Input High Voltage, TTL Mode Output Low Voltage, High Drive[5] Output Low Voltage, High Output High Voltage[6] Drive[5] Output Low Voltage, Low Drive[6] I/O-pin Supply = 2.9-3.6V I/O-pin Supply = 4.0-5.5V IOL1 = 50 mA IOL1 = 25 mA IOL2 = 8 mA IOH = 2 mA VCC - 0.5 50 2.0 0.8 0.4 0.4 SDATA or SCLK pins SDATA, SCLK pins, PS/2 Enabled 3 4 40% 30% 3% 0.4 7 12 65% 55% 10% 0.8 V K K VCC VCC VCC V V V V V V pF General Conditions Min. Typical Max. Unit
General Purpose I/O Interface
Maximum load capacitance
27.0
Clock TECLKDC TECLK1 TECLK2
AC Characteristics
Description External Clock Duty Cycle External Clock Frequency External Clock Frequency External clock is the source of the CPUCLK External clock is not the source of the CPUCLK 10Hz to 100MHz at CLOAD = 1F CLOAD = 200 pF CLOAD = 600 pF CLOAD = 200 pF CLOAD = 600 pF 80 1.3 Ave. Bit Rate (1.5 Mbps 1.5%) To next transition To pair transition 1.4775 -75 -45 -40 75 300 125 2.0 1.5225 75 45 100 75 300 Conditions Min. 45 0.187 0 Typical Max. 55 24 24 Unit % MHz MHz
Parameter
3.3V Regulator VORIP USB Driver TR1 TR2 TF1 TF2 TR VCRS TDRATE TDJR1 TDJR2 TDEOP Transition Rise Time Transition Rise Time Transition Fall Time Transition Fall Time Rise/Fall Time Matching Output Signal Crossover Voltage Low-speed Data Rate Receiver Data Jitter Tolerance Receiver Data Jitter Tolerance Differential to EOP Transition Skew ns ns ns ns % V Mbps ns ns ns Output Ripple Voltage 200 mVp-p
USB Data Timing
Document 38-08035 Rev. *I
Page 62 of 74
[+] Feedback
CY7C63310 CY7C638xx
27.0
TEOPR1 TEOPR2 TEOPT TUDJ1 TUDJ2 TLST TFPS2 TR_GPIO TF_GPIO SPI Timing TSMCK TSSCK TSCKH TSCKL TMDO TMDO1 TMSU TMHD TSSU TSHD TSDO TSDO1 TSSS TSSH
1
AC Characteristics (continued)
Description EOP Width at Receiver EOP Width at Receiver Source EOP Width Differential Driver Jitter Differential Driver Jitter Width of SE0 during Diff. Transition SDATA/SCK Transition Fall Time Output Rise Time Output Fall Time Measured between 10 and 90% Vdd/Vreg with 50 pF load Measured between 10 and 90% Vdd/Vreg with 50 pF load FCPUCLK/6 High for CPOL = 0, Low for CPOL = 1 Low for CPOL = 0, High for CPOL = 1 SCK to data valid Time before leading SCK edge 125 125 -25 100 50 50 50 50 SCK to data valid Time after SS LOW to data valid Before first SCK edge After last SCK edge 150 150 100 100 50 50 To next transition To pair transition Conditions Rejects as EOP Accept as EOP 675 1.25 -95 -95 1.5 95 95 210 300 50 15 Min. Typical Max. 330 Unit ns ns s ns ns ns ns ns ns
Parameter
Non-USB Mode Driver Characteristics GPIO Timing
SPI Master Clock Rate SPI Slave Clock Rate SPI Clock High Time SPI Clock Low Time Master Data Output Time[5] Master Data Output Time, First bit with CPHA = 0 Master Input Data Set-up time Master Input Data Hold time Slave Input Data Set-up Time Slave Input Data Hold Time Slave Data Output Time Slave Data Output Time, First bit with CPHA = 0 Slave Select Set-up Time Slave Select Hold Time
2 2.2
MHz MHz ns ns ns ns ns ns ns ns ns ns ns ns
Figure 27-1. Clock Timing TCYC TCH
CLOCK
TCL
Note 5. In Master mode first bit is available 0.5 SPICLK cycle before Master clock edge available on the SCLK pin.
Document 38-08035 Rev. *I
Page 63 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 27-2. GPIO Timing Diagram
90%
GPIO Pin Output Voltage
10% TR_GPIO TF_GPIO
Figure 27-3. USB Data Signal Timing
Voh Vcrs Vol
D+
TR
90% 10% 90%
TF
10%
D-
Figure 27-4. Receiver Jitter Tolerance
TPERIOD Differential Data Lines
TJR TJR1 TJR2
Consecutive Transitions N * TPERIOD + TJR1 Paired Transitions N * TPERIOD + TJR2
Document 38-08035 Rev. *I
Page 64 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 27-5. Differential to EOP Transition Skew and EOP Width
TPERIOD Differential Data Lines
Crossover Point
Crossover Point Extended
Diff. Data to SE0 Skew N * TPERIOD + TDEOP
Source EOP Width: TEOPT Receiver EOP Width: TEOPR1, TEOPR2
Figure 27-6. Differential Data Jitter
TPERIOD Differential Data Lines
Crossover Points
Consecutive Transitions N * TPERIOD + TxJR1 Paired Transitions N * TPERIOD + TxJR2
Document 38-08035 Rev. *I
Page 65 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 27-7. SPI Master Timing, CPHA = 1
SS
(SS is under firmware control in SPI Master mode)
TSCKL
SCK (CPOL=0)
TSCKH
SCK (CPOL=1)
TMDO
MOSI
MSB
LSB
MISO
MSB
LSB
TMSU TMHD
Figure 27-8. SPI Slave Timing, CPHA = 1
SS
TSSS TSCKL TSSH TSCKH
SCK (CPOL=0)
SCK (CPOL=1)
MOSI
TSDO
MSB
LSB
TSSU TSHD
MSB LSB
MISO
Document 38-08035 Rev. *I
Page 66 of 74
[+] Feedback
CY7C63310 CY7C638xx
Figure 27-9. SPI Master Timing, CPHA = 0
SS
(SS is under firmware control in SPI Master mode)
TSCKL
SCK (CPOL=0)
TSCKH
SCK (CPOL=1)
TMDO1 TMDO
MSB LSB
MOSI
MISO
MSB
LSB
TMSU TMHD Figure 27-10. SPI Slave Timing, CPHA = 0
SS
TSSS TSCKL TSSH TSCKH
SCK (CPOL=0)
SCK (CPOL=1)
MOSI
MSB
LSB
TSSU TSHD TSDO1 TSDO
MSB LSB
MISO
28.0
Ordering Information
Ordering Code FLASH Size 8K 8K 8K RAM Size 256 256 256 32-QFN 24-SOIC 24-QSOP Page 67 of 74
[+] Feedback
Package Type
CY7C63833-LFXC CY7C63823-SXC CY7C63823-QXC Document 38-08035 Rev. *I
CY7C63310 CY7C638xx
28.0 Ordering Information (continued)
Ordering Code CY7C63813-PXC CY7C63813-SXC CY7C63803-SXC CY7C63801-PXC CY7C63801-SXC CY7C63310-PXC CY7C63310-SXC FLASH Size 8K 8K 8K 4K 4K 3K 3K RAM Size 256 256 256 256 256 128 128 18-PDIP 18-SOIC 16-SOIC 16-PDIP 16-SOIC 16-PDIP 16-SOIC Package Type
29.0
Package Diagrams
Figure 29-1. 16-Lead(300-Mil) Molded DIP P1
51-85009-*A
Document 38-08035 Rev. *I
Page 68 of 74
[+] Feedback
CY7C63310 CY7C638xx
29.0 Package Diagrams (continued)
Figure 29-2. 16-Lead (150-Mil) SOIC S16.15
PIN 1 ID
8
1 DIMENSIONS IN INCHES[MM] MIN. MAX. REFERENCE JEDEC MS-012
0.150[3.810] 0.157[3.987] 0.230[5.842] 0.244[6.197]
PACKAGE WEIGHT 0.15gms
PART # S16.15 STANDARD PKG. SZ16.15 LEAD FREE PKG. 9 16
0.386[9.804] 0.393[9.982]
SEATING PLANE
0.010[0.254] 0.016[0.406]
X 45
0.061[1.549] 0.068[1.727] 0.004[0.102] 0.050[1.270] BSC 0.0138[0.350] 0.0192[0.487] 0.004[0.102] 0.0098[0.249]
0~8
0.016[0.406] 0.035[0.889]
0.0075[0.190] 0.0098[0.249]
51-85068-*B
Figure 29-3. 18-Lead(300-Mil) Molded DIP P3
51-85010-*B
Document 38-08035 Rev. *I
Page 69 of 74
[+] Feedback
CY7C63310 CY7C638xx
29.0 Package Diagrams (continued)
18 Lead (300 Mil) SOIC - S3
PIN 1 ID
9 1
Figure 29-4. 18-Lead(300-Mil) Molded SOIC S3
0.291[7.391] 0.300[7.620]
DIMENSIONS IN INCHES[MM]
*
0.394[10.007] 0.419[10.642]
MIN. MAX.
REFERENCE JEDEC MO-119
10
18
0.026[0.660] 0.032[0.812]
PART # S18.3 STANDARD PKG. SZ18.3 LEAD FREE PKG.
0.447[11.353] 0.463[11.760]
SEATING PLANE
0.092[2.336] 0.105[2.667]
0.004[0.101] 0.050[1.270] TYP. 0.013[0.330] 0.019[0.482] 0.004[0.101] 0.0118[0.299]
*
0.015[0.381] 0.050[1.270] 0.0091[0.231] 0.0125[0.317]
*
51-85023-*B
Document 38-08035 Rev. *I
Page 70 of 74
[+] Feedback
CY7C63310 CY7C638xx
29.0 Package Diagrams (continued)
Figure 29-5. 24-Lead (300-Mil) SOIC S13
DIMENSIONS IN INCHES JEDEC STD REF MO-119
51-85025-*C
Figure 29-6. 24-lead QSOP O241
S
0.033 REF.
12 1
PIN 1 ID
0.228 0.244
0.150 0.157
DIMENSIONS IN INCHES MIN. MAX.
13
24
0.337 0.344 SEATING PLANE 0.053 0.069
0.004
0.007 0.010
0.004 0.010
0.008 0.012 0.025 BSC.
0.016 0.034
0-8
51-85055-*B
Document 38-08035 Rev. *I
Page 71 of 74
[+] Feedback
CY7C63310 CY7C638xx
29.0 Package Diagrams (continued)
Figure 29-7. 32-Lead QFN Package
DIMENSIONS IN mm MIN. MAX.
0.05 4.90 5.10 4.65 4.85 N 0.93 MAX. 0.05 MAX. 0.80 MAX. 0.20 REF. 3.70 0.230.05 N PIN1 ID 0.20 R. 0.45 1 2 4.90 5.10 C
1 2 0.50 DIA. 4.65 4.85
3.70
3.50
0-12 C SEATING PLANE
0.30-0.50 0.50 3.50
0.420.18 (4X)
TOP VIEW
SIDE VIEW
BOTTOM VIEW
JEDEC # MO-220 Package Weight: 0.054 grams
51-85188-*A
PSoC is a trademark of Cypress MicroSystems. enCoRe is a trademark of Cypress Semiconductor Corporation. All product and company names mentioned in this document are the trademarks of their respective holders.
Document 38-08035 Rev. *I
Page 72 of 74
[+] Feedback
CY7C63310 CY7C638xx
30.0 Document History Page
Document Title: CY7C63310/CY7C638xx enCoReTM II Low-Speed USB Peripheral Controller Document Number: 38-08035 Rev. ** *A *B *C ECN No. 131323 221881 271232 299179 Issue Date 12/11/03 See ECN See ECN See ECN Orig. of Change XGR KKU BON BON New data sheet Added Register descriptions and package information, changed from advance information to preliminary Reformatted Updated with the latest information Corrected 24-PDIP pinout typo in Table 5.1 Added Table 10-1 Updated Table 9-5, Table 10-3, Table 13-1, Table 17-2, Table 17-4, Table 17-6. and Table 15-2. Added various updates to the GPIO Section (Section 14.0) Corrected Table 15-3. Corrected Figure 27-7 and Figure 27-8. Added the 16-pin PDIP package diagram (Section 29.0) Introduction section: Last para removed Low-voltage reset. There is no LVR there is only LVD (Low voltage detect). explained more about LVD and POR Changed capture pins from P0.0,P0.1 to P0.5,P0.6 Table 6-1: Changed table heading (Removed Mnemonics and made as Register names). Table 9-5: Included #of rows for different flash sizes Section10-1: Changed CPUCLK selectable options from n=0-5,7,8 to n=0-5,7 Clocks section: Changed ITMRCLK division to 1,2,3,4. updated the sources to ITMRCLK, TCAPCLKs. Mentioned P17 is TTL enabled permanently. Corrected FRT, PIT data write order. Updated INTCLR,INTMSK registers. in the register table also. DC spec sheet: changed LVR to LVD included max min programmable trip points based on char data. Updated the 50ma sink pins on 638xx, 63903. Keep-alive voltage mentioned corresponding to Keep-alive current of 20uA. Included Notes regarding VOL,VOH on P1.0,P1.1 and TMDO spec. AC Specs: TMDO1, TSDO1 In description column changed Phase to 0 Section 5: Removed the VREG from the CY7C63310 and CY7C63801 Removed SCLK and SDATA. Created a separate pinout diagram for the CY7C63813 Added the GPIO Block Diagram (Figure 14-1.) Table 10-4: Changed the Sleep Timer Clock unit from 32 KHz count to Hz Table 21-1: Added more descriptions to the register Corrected VIH TTL value in DC Characteristics table Updated VIL TTL value Added footnote to pin description table for D+/D- pins Added Typical Values to Low Voltage Detect table Corrected Pin label on 16-pin PDIP package Corrected minor typos Corrected pin assignment for the 24-pin QSOP package - GPIO port 3 in Table 5-1: Pin Assignment New Assignments: Pin 19 assigned to P3.0 and pin 20 to P3.1 Table 17.7 INT_MASK1 changed to 0xE1 Table 17.8 INT_MASK0 changed to 0xE0 Table 24.0-Register Summary, address E0 assigned to INT_MASK0 and address E1 assigned to INT_MASK1 Minor text changes to make document more readable Removed CY7C639xx Removed CY7C639xx from Ordering Information Table Added text concerning current draw for P0.0 and P0.1 in Table 5-1 Corrected Figure 9-2 to represent single stack Added comment about availability of 3.3V I/O on P1.3-P1.6 in Table 5-1 Added information on Flash endurance and data retention to section 9.3 Added block diagrams and timing diagrams Added CY7C638xx die form diagrams, Pad assignment tables and Ordering information Keyboard references removed CY7C63923-XC die diagram removed, removed references to the 639xx parts Updated part numbers in the header Description of Change
*D
322053
See ECN
TVR
BON
*E
341277
See ECN
BHA
*F
408017
See ECN
TYJ
*G
424790
See ECN
TYJ
Document 38-08035 Rev. *I
Page 73 of 74
(c) Cypress Semiconductor Corporation, 2006. The information contained herein is subject to change without notice. Cypress Semiconductor Corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a Cypress product. Nor does it convey or imply any license under patent or other rights. Cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement with Cypress. Furthermore, Cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges.
[+] Feedback
CY7C63310 CY7C638xx
30.0 Document History Page (continued)
Document Title: CY7C63310/CY7C638xx enCoReTM II Low-Speed USB Peripheral Controller Document Number: 38-08035 Rev. *H ECN No. 491711 Issue Date See ECN Orig. of Change TYJ Description of Change Minor text changes 32-QFN part added Removed 638xx die diagram and die form pad assignment Removed GPIO port 4 configuration details Corrected GPIO characteristics of P0.0 and P0.1 to P1.0 and P1.1 respectively Minor text changes Removed all residual references to external crystal oscillator and GPIO4 Documented the dedicated 3.3V regulator for USB transceiver Documented bandgap/voltage regulator behavior on wake up Voltage regulator line/load regulation documented USB Active and PS2 Data low interrupt trigger conditions documented. GPIO capacitance and timing diagram included Method to clear Capture Interrupt Status bit discussed Sleep and Wake up sequence documented. EP1MODE/EP2MODE register issue discussed
*I
504691
See ECN
TYJ
Document 38-08035 Rev. *I
Page 74 of 74
[+] Feedback

▲Up To Search▲

Price & Availability of CY7C63813-PXC

	To Download CY7C63813-PXC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .